Toolkits > com.ibm.streamsx.eventstore 1.2.0 > com.ibm.streamsx.eventstore > EventStoreSink
The EventStoreSink inserts IBM Streams tuples in to an IBM Db2 Event Store table.
Required: connectionString, databaseName, tableName
Optional: batchSize, configObject, eventStorePassword, eventStoreUser, frontEndConnectionFlag, maxNumActiveBatches, nullMapString, partitioningKey, preserveOrder, primaryKey
Port that ingests tuples which are inserted into Db2 Event Store database table. The tuple field types and positions in the IBM Streams schema must match the field names in your IBM Db2 Event Store table schema exactly.Incoming tuples are processed in batches, where the processing will be to send rows to IBM Db2 Event Store, and is driven by the size of the batch. A batch is processed when it reaches at least the batch size.
Port that optionally produces tuple insert results. This output port is intended to output the information on whether a tuple was successful or not when it was inserted into the database. EventStoreSink looks for a Boolean field called _Inserted_ in the output stream. EventStoreSink sets the field to true if the data was successfully inserted and false if the insert failed. Besides the _Inserted_ column, the output will include the original tuple attributes (from input stream) that was processed by the EventStoreSink operator.
Required: connectionString, databaseName, tableName
Optional: batchSize, configObject, eventStorePassword, eventStoreUser, frontEndConnectionFlag, maxNumActiveBatches, nullMapString, partitioningKey, preserveOrder, primaryKey
Specifies the batch size for the number of rows that will be batched in the operator before the batch is inserted into IBM Db2 Event Store by using the batchInsertAsync method. If you do not specify this parameter, the batchSize defaults to the estimated number of rows that could fit into an 8K memory page.
Specify the application configuration name. An application configuration can be created in the Streams Console or using the streamtool mkappconfig ... <configObject name>. If you specify parameter values (properties) in the configuration object, they override the values that are configured for the EventStoreSink operator. Supported properties are: eventStoreUser and eventStorePassword
Specifies the IBM Db2 Event Store connection endpoint as a set of IP addresses and ports: <IP>:<port>. Separate multiple entries with a comma.
The name of an existing IBM Db2 Event Store database in order to connect
Password for the IBM Db2 Event Store User in order to connect. If you do not specify the eventStorePassword parameter or an empty string is set, then a default is used.
Name of the IBM Db2 Event Store User in order to connect. If you do not specify the eventStoreUser parameter or an empty string is set, then a default is used.
Set to true to connect through a Secure Gateway for Event Store Enterprise Edition version >= 1.1.2 and Developer Edition version > 1.1.4
Set the maximum number of active batches.
Set the null map JSON represented by a string.
Partitioning key for the table. A string of attribute names separated by commas. The order of the attribute names defines the order of entries in the sharding key for the IBM Db2 Event Store table. The attribute names are the names of the fields in the stream. The partitioningKey parameter is used only if the table does not yet exist in the IBM Db2 Event Store database. If you do not specify this parameter or if the key string is empty, the key defaults to making the first column in the stream as the shard key. For example, "col1, col2, col3"
Preserve order if true
Primary key for the table. A string of attribute names separated by commas. The order of the attribute names defines the order of entries in the primary key for the IBM Db2 Event Store table. The attribute names are the names of the fields in the stream. The primaryKey parameter is used only, if the table does not yet exist in the IBM Db2 Event Store database. If you do not specify this parameter, the resulting table has an empty primary key.
The name of the table into which you want to insert data from the IBM Streams application. If the table does not exist, the table is automatically created in IBM Db2 Event Store.
Number of batches inserted together
Time it takes to perform a successful batch insert
Number of active insert requests
Number of tuples that failed to get written to IBM Db2 Event Store
Number of tuples that were written to IBM Db2 Event Store successfully