The Camel HBase Consumer, will perform repeated scan on the specified HBase table and will return the scan results as part of the message. You can either specify header mapping (default) or body mapping. The later will just add the org.apache.camel.component.hbase.model.HBaseData as part of the message body.
hbase://table[?options]
You can specify the columns that you want to be return and their types as part of the uri options:
hbase:mutable?family=name&qualifer=first&valueType=java.lang.String&family=address &qualifer=number&valueType2=java.lang.Integer&rowType=java.lang.Long
The example above will create a model object that is consisted of the specified fields and the scan results will populate the model object with values. Finally the mapping strategy will be used to map this model to the camel message.
Name |
Default Value |
Description |
---|---|---|
|
|
Milliseconds before the first polling starts. |
|
|
Milliseconds before the next poll. |
|
|
Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
|
|
time unit for |
|
|
Camel 2.8: The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. |
|
|
The HBase operation to perform. Supported
values: |
|
|
The maximum number of rows to scan. Supported
operations:
|
|
|
The strategy to use for mapping Camel messages to HBase columns. Supported
values: |
|
|
The class name of a custom mapping strategy implementation. |
|
|
A list of filters. Supported operations:
|
|
|
If the option is true, Camel HBase Consumer will remove the rows which it processes. |
Header mapping options:
Name |
Default Value |
Description |
---|---|---|
|
The id of the row. This has limited use as the row usually changes per Exchange. | |
|
|
The type to covert row id to. Supported
operations: |
|
The column family. *upports a number suffix for referring to more than one columns | |
|
The column qualifier. *Supports a number suffix for referring to more than one columns | |
|
The value. Supports a number suffix for referring to more than one columns | |
|
|
An instance of org.apache.camel.component.hbase.model.HBaseRow which describes how each row should be modeled |
If the role of the rowModel is not clear, it allows you to construct the HBaseRow modle programmatically instead of "describing" it with uri options (such as family, qualifier, type etc).