HBase Input
Overview
The HBase Input operator converts specified columns in an HBase table into input fields of the same quantity.
Input and Output
- Input: HBase table columns
- Output: fields
Parameter Description
Parameter |
Description |
Type |
Mandatory |
Default Value |
---|---|---|---|---|
Hbase Table Type |
HBase table type. The options include normal (common HBase table) and phoenix. |
enum |
Yes |
normal |
HBase table name |
HBase table name. Only one HBase table is supported. |
string |
Yes |
None |
HBase input fields |
HBase input information:
|
map |
Yes |
None |
Data Processing Rule
- If the HBase table name does not exist, the job fails to be submitted.
- If the configured column names are inconsistent with the HBase table column names, the data cannot be read and the number of imported data records is 0.
- If the number of input field columns is greater than the number of field columns actually included in the original data, all data becomes dirty data.
- If the field value does not match the actual type, the data in the line will become dirty data.
Example
Use the data export from HBase to sqlserver2014 as an example.
In sqlserver2014, run the following statement to create an empty data test_1 for storing HBase data:
create table test_1 (id int, name text, value text);
Configure the HBase Input operator to generate fields A, B, and C.
After the database connection is set up, click
. The system will automatically read fields in the database and select required fields for adding. You only need to optimize or modify the fields manually based on service scenarios.Performing this operation will overwrite existing data in the table.
Use the Table Out operator to export A, B, and C to the test_1 table.
select * from test_1;
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot