Enter information about the columns in the HBase table that you want to map. The names of the incoming fields must match the aliases of fields defined in the mapping. There can be fewer incoming fields than defined in the mapping. However, if there are more incoming fields than defined, then an error will occur. One of the incoming fields must match the key defined in the mapping.
A valid mapping must define metadata for the key of the source HBase table. Because no name is given to the key of an HBase table, you must specify an Alias.
An Alias is optional for non-key columns, but you must specify the Column family and Column name. If an Alias is not supplied, then the Column name is used.
You must supply Type information for all the fields.
The key fields table includes the following columns:
| Column | Description |
|---|---|
| # | The order of the mapping operation. |
| Alias | The name you want to assign to the HBase table key. This value is required for the table key column, but optional for non-key columns. |
| Key | Specify if the field is the table's key. The values are Y and N. |
| Column family | The column family in the HBase source table that the field belongs to. Non-key columns must specify a column family and column name. |
| Column name | The name of the column in the HBase table. |
| Type |
The data type for the column. When the Key value is set to
Y, the following key column values display in the
drop-down list:
When the Key value is set to
N, the following non-key column values display in the
drop-down list:
|
| Indexed values | Comma-separated data in this field defines the values for string columns. |
To save the mapping in HBase, click Save mapping. You are prompted to correct any missing information in the mapping definition before proceeding.
- If you provided valid connection details and named the mapping, the mapping is saved to the cluster in HBase.
- If you only need the mapping locally, then the connection details and mapping name are not required and the mapping information is serialized automatically into the transformation metadata.
To delete a mapping in HBase, click Delete mapping. The current named mapping in the current named table is deleted from the mapping table, but the actual HBase table remains.
To partially populate the key fields table with fields that define a tuple mapping, click Create a tuple template. Tuple output mode inserts all the data in wide HBase rows where the number of columns may vary from row to row. It assumes that all column values are of the same type. A tuple mapping consists of the following output fields:
- KEY
- Family
- Column
- Value
- Timestamp
The type for "Family" is preconfigured to String and the type for "Timestamp" is preconfigured to Long. You must provide the types for "KEY", "Column" (column name) and "Value" (column value). The default behavior is to output all column values in all column families.