To HBase/CloudTable
Sample JSON File
"to-config-values": { "configs": [ { "inputs": [ { "name": "toJobConfig.table", "value": "rf_to" }, { "name": "toJobConfig.storageType", "value": "PUTLIST" }, { "name": "toJobConfig.columns", "value": "AA:AA&BB:BB&CC:CC&DD:DD" }, { "name": "toJobConfig.rowKeyColumn", "value": "AA:AA" }, { "name": "toJobConfig.isOverride", "value": "false" }, { "name": "toJobConfig.isRowkeyRedundancy", "value": "false" }, { "name": "toJobConfig.algorithm", "value": "NONE" }, { "name": "toJobConfig.writeToWAL", "value": "true" }, { "name": "toJobConfig.transType", "value": "false" } ], "name": "toJobConfig" } ] }
Parameter Description
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
toJobConfig.table |
Yes |
String |
Name of the table to which data is written. For example, TBL_EXAMPLE. |
toJobConfig.storageType |
Yes |
Enumeration |
Mode for writing data to an HBase table. The options are as follows:
|
toJobConfig.columns |
No |
String |
Columns to be extracted. Use & to separate column numbers and : to separate column families and columns. For example, cf1:c1&cf2:c2. |
toJobConfig.rowKeyColumn |
Yes |
String |
Columns serve as rowkeys. Use & to separate column numbers and : to separate column families and columns. For example, cf1:c1&cf2:c2. |
toJobConfig.isOverride |
No |
Boolean |
Whether to clear data when data is imported in BULKLOAD mode. For example, true. |
toJobConfig.delimiter |
No |
String |
Delimiter used for separating columns when multiple columns are used as rowkeys. For example, vertical bars (|). |
toJobConfig.isRowkeyRedundancy |
No |
Boolean |
Whether to write rowkey data to the HBase column at the same time |
toJobConfig.algorithm |
No |
Enumeration |
Compression algorithm used when a new HBase table is created. The Snappy and GZ algorithms are supported. The default value is None. |
toJobConfig.writeToWAL |
No |
Boolean |
Whether to enable Write Ahead Log (WAL) of HBase. The options are as follows:
|
toJobConfig.transType |
No |
Boolean |
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.