IBMStreams com.ibm.streamsx.hbase Toolkit > com.ibm.streamsx.hbase 3.9.3 > com.ibm.streamsx.hbase > HBASEPut
The HBASEPut operator puts tuples into an Hbase table. It includes support for checkAndPut. If the value is a primitive type, a Put method must have a row, columnFamily, columnQualifier,and value specified. The row and value are derived from the input tuple, which is specified by the rowAttrName and valueAttrName parameters. The columnFamily and columnQualifier can be specified in the same way, by using the columnFamilyAttrName and columnQualifierAttrName parameters. Alternatively, they can be the same for all tuples, by setting the staticColumnFamily and staticColumnQualifier parameters.
() as allSink = HBASEPut(full)
{
param
tableName : "streamsSample_lotr" ;
rowAttrName : "character" ;
columnFamilyAttrName : "colF" ;
columnQualifierAttrName : "colQ" ;
valueAttrName : "value" ;
}
If the value is a tuple type, then the attribute names of the tuple are interpreted as the columnQualifiers for the correponding values. Here is an snippet from the PutRecord sample application. We create the toHBASE stream:
stream<rstring key, tuple<rstring title, rstring author_fname,
rstring author_lname, rstring year, rstring rating> bookData> toHBASE =
Functor(bookStream)
{
//// ...
}
Then we can use HBASEPut as follows:
() as putsink = HBASEPut(toHBASE)
{
param
rowAttrName : "key" ;
tableName : "streamsSample_books" ;
staticColumnFamily : "all" ;
valueAttrName : "bookData" ;
}
To support locking, HBASE supports a conditional put operation. This operator supports that operation by using the checkAttrName parameter. If that parameter is set, then the input attribute it refers to must be a valid check type. For more information, see the parameter description. On a put operation, the condition is checked.If it passes, the put operation happens; if not, the put operation fails. To check the success or failure of the put operation, use an optional output port. The attribute that is specified in the successAttr parameter on the output port is set to true if the put operation occurs, and false otherwise.
Behavior in a consistent region
The HBASEPut operator can be in a consistent region, but it cannot be the start of a consistent region. At drain points, it flushes its internal buffer. At resets, it clears its internal buffer.The operator ensures at-least-once tuple processing, but does not guarentee exactly-once tuple processing. If there is a reset, the same entry might be put twice. If you use this operator with the HBASEGet operator to do a get, modify, and put operation on the same entry in a consistent region, you could end up doingthe modification twice. That scenario is not recommended. If you need exactly-once tuple processing, it might be possible to use checkAndPut with sequence numbers.
Required: rowAttrName, valueAttrName
Optional: Timestamp, TimestampAttrName, authKeytab, authPrincipal, batchSize, checkAttrName, columnFamilyAttrName, columnQualifierAttrName, enableBuffer, hbaseSite, staticColumnFamily, staticColumnQualifier, successAttr, tableName, tableNameAttribute
Tuple to put into HBASE
Optional port for success or failure information.
Optional port for error information. This port submits an error message and a tuple, when an error occurs while HBase actions.
Required: rowAttrName, valueAttrName
Optional: Timestamp, TimestampAttrName, authKeytab, authPrincipal, batchSize, checkAttrName, columnFamilyAttrName, columnQualifierAttrName, enableBuffer, hbaseSite, staticColumnFamily, staticColumnQualifier, successAttr, tableName, tableNameAttribute
This parameter specifies the timestamp in milliseconds (INT64). The timestamp allows for versioning of the cells. Everytime HBaes make a PUT on a table it set the timestamp. By default this is the current time in milliseconds, but you can set your own timestamp as well with this parametr. Cannot be used with TimestampAttrName
Name of the attribute on the input tuple containing the timestamp in milliseconds. Cannot be used with Timestamp.
The authKeytab parameter specifies the kerberos keytab file that is created for the principal.
The authPrincipal parameter specifies the Kerberos principal, which is typically the principal that is created for HBase server
This parameter has been deprecated as of Streams 4.2.0. The enableBuffer parameter should be used instead. The batchSize parameter indicates the maximum number of Puts to buffer before sending to HBase. Larger numbers are more efficient, but increase the risk of lost changes on operator crash. In a consistent region, a drain flushes the buffer to HBase.
Name of the attribute specifying the tuple to check for before applying the Put or Delete. The type of the attribute is tuple with attributes columnFamily and columnQualifier, or a tuple with attributes columnFamily, columnQualifier, and value. In the first case, the Put or Delete will be allowed to proceed only when there is no entry for the row, columnFamily, columnQualifer combination. When the the type of the attribute given by checkAttrName contains an attribute value, the Put or Delete operation will only succeed when the entry specified the row, columnFamily, and columnQualifier has the given value.
Name of the attribute on the input tuple containing the columnFamily. Cannot be used with staticColumnFmily.
Name of the attribute on the input tuple containing the columnQualifier. Cannot be used with staticColumnQualifier.
When set to true, this parameter can improve the performance of the operator because tuples received by the operator will not be immediately forwarded to the HBase server. The buffer is flushed and the tuples are sent to HBase when one of the following three conditions is met: the buffer's size limit is reached, or a window marker punctuation is received by the operator, or, during a drain operation if the operator is present in a consistent region. The buffer size is set in hbase-site.xml using the hbase.client.write.buffer property. Note that although enabling buffering improves performance, there is a risk of data loss if there is a system failure before the buffer is flushed. By default, enableBuffer is set to false. This parameter cannot be combined with the checkAttrName parameter, since checkAndPut operations in HBase are not buffered.
The hbaseSite parameter specifies the path of hbase-site.xml file. This is the recommended way to specify the HBASE configuration. If not specified, then HBASE_HOME must be set when the operator runs, and it will use $HBASE_SITE/conf/hbase-site.xml
Name of the attribute on the input tuple containing the row. It is required.
If this parameter is specified, it will be used as the columnFamily for all operations. (Compare to columnFamilyAttrName.) For HBASEScan, it can have cardinality greater than one.
If this parameter is specified, it will be used as the columnQualifier for all tuples. HBASEScan allows it to be specified multiple times.
Attribute on the output port to be set to true if the check passes and the action is successful
Name of the HBASE table. It is an optional parameter but one of these parameters must be set in opeartor: 'tableName' or 'tableNameAttribute'. Cannot be used with 'tableNameAttribute'. If the table does not exist, the operator will throw an exception
Name of the attribute on the input tuple containing the tableName. Use this parameter to pass the table name to the operator via input port. Cannot be used with parameter 'tableName'. This is suitable for tables with the same schema.
This parameter specifies the name of the attribute that contains the value that is put into the table.