# tHBaseOutput Standard properties

These properties are used to configure tHBaseOutput running in the Standard Job framework.

The Standard tHBaseOutput component belongs to the Big Data and the Databases NoSQL families.

The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric.

## Basic settings

| Properties | Description |
| --- | --- |
| Property type | Either Built-In or Repository.<br><br><br>Built-In: No property data stored centrally.<br><br><br>Repository: Select the repository file where the<br>properties are stored. |
| ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/Save_Icon.png) | Click this icon to open a database connection wizard and store the<br>database connection parameters you set in the component Basic<br>settings view.<br><br>For more information about setting up and storing database connection<br>parameters, see [Centralizing database metadata](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/centralizing-database-metadata). |
| Use an existing connection | Select this check box and in the Component<br>List drop-down list, select the desired connection component to<br>reuse the connection details you already defined. |
| HBase version | Select the HBase version of the distribution you are using. |
| Hadoop version | Select the Hadoop version of the distribution you are using. |
| Zookeeper quorum | Type in the name or the URL of the ZooKeeper service you use to coordinate the<br>transaction between your Talend Studio and<br>your database. Note that when you configure the ZooKeeper, you might need to explicitly<br>set the *zookeeper.znode.parent* property to define the path to the<br>root Znode that contains all the Znodes created and used by your database; then select<br>the Set Zookeeper znode parent check box to define<br>this property. |
| Zookeeper client port | Type in the number of the client listening port of the ZooKeeper service you<br>are using. |
| Use kerberos authentication | If the database to be used is running with Kerberos security, select this<br>checkbox, then, enter the principal names in the HBase Master<br>principal and HBase Region Server principal<br>fields. You should be able to find the information in the *hbase-site.xml* file of the cluster to be used.<br><br>If you need to use a Kerberos keytab file to log in, select Use a keytab to authenticate. A keytab file contains<br>pairs of Kerberos principals and encrypted keys. You need to enter the principal to<br>be used in the Principal field and the access<br>path to the keytab file itself in the Keytab<br>field. This keytab file must be stored in the machine in which your Job actually<br>runs, for example, on a Talend JobServer.<br><br>Note that the user that executes a keytab-enabled Job is not necessarily<br>the one a principal designates but must have the right to read the keytab file being<br>used. For example, the username you are using to execute a Job is *user1* and the principal to be used is *guest*; in this<br>situation, ensure that *user1* has the right to read the keytab<br>file to be used. |
| Schema and Edit<br>schema | <ul> <li> <p>A schema is a row description. It defines the number of fields            (columns) to be processed and passed on to the next component. When you create a Spark            Job, avoid the reserved word <kbd>line</kbd> when naming the            fields.</p> <p>Click <span>Edit        schema</span> to make changes to the schema. If the current schema is of the <span>Repository</span> type, three options are available:</p> <ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> </li> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> <p>When the schema to be reused has default values that are            integers or functions, ensure that these default values are not enclosed within            quotation marks. If they are, you must remove the quotation marks manually.</p> <p>For more information, see <a href="https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/retrieving-table-schemas?tocId=_C1~eFOlN~GM_JR2qkBYZg" target="_blank">Retrieving table schemas</a>.</p> </li> </ul> |
| Specify namespace | Select this check box if you want to specify a namespace, and enter the name<br>of the namespace you want to create in the Namespace<br>parameter. |
| Table name | Type in the name of the HBase table you need create. |
| Action on table | Select the action you need to take for creating an HBase<br>table. |
| Custom Row Key | Select this check box to use the customized row keys. Once<br>selected, the corresponding field appears. Then type in the user-defined row<br>key to index the rows of the HBase table being created.<br><br>For example, you can type in "France"+Numeric.sequence("s1",1,1) to produce the row key series:<br>France1, France2, France3 and so on. |
| Families | Complete this table to map the columns of the table to be used with the schema columns you<br>have defined for the data flow to be processed.<br><br>The Column column of this table is<br>automatically filled once you have defined the schema; in the Family name column, enter the column families you want to create or use<br>to group the columns in the Column column. For more<br>information about a column family, see [Column families](http://hbase.apache.org/0.94/book/columnfamily.html) from Apache documentation. |
| Custom timestamp column | Select a Long column from your schema to provide<br>timestamps for the HBase columns to be created or updated by<br>tHBaseOutput. |
| Die on error | This check box is cleared by default, meaning to skip the row on<br>error and to complete the process for error-free rows. |

## Advanced settings

| Properties | Description |
| --- | --- |
| Use batch mode | Select this check box to activate the batch mode for data processing. |
| Batch size | Specify the number of records to be processed in each batch.<br><br>This field is available only when the Use batch mode<br>check box is selected. |
| Properties | If you need to use custom configuration for your database, complete this<br>table with the property or properties to be customized. Then at runtime, the customized<br>property or properties will override the corresponding ones used by Talend Studio.<br><br>For example, you need to define the value of the *dfs.replication* property as *1* for the<br>database configuration. Then you need to add one row to this table using the plus button and<br>type in the name and the value of this property in this row.<br><br>Information noteNote:<br><br>This table is not available when you are using an existing<br>connection by selecting the Using an<br>existing connection check box in the Basic settings view. |
| tStatCatcher Statistics | Select this check box to collect log data at the component<br>level. |
| Family parameters | Type in the names and, when needs be, the custom performance options of the<br>column families to be created. These options are all attributes defined by the<br>HBase data model. For more information about a column family, see [Column families](http://hbase.apache.org/0.94/book/columnfamily.html) from Apache documentation.<br><br>Information noteNote: The parameter Compression type allows you to select the<br>format for output data compression. |

## Global Variables

| Variables | Description |
| --- | --- |
| Global Variables | NB\_LINE: the number<br>of rows read by an input component or transferred to an output component. This is an<br>After variable and it returns an integer.<br><br><br>ERROR\_MESSAGE: the error message generated by the<br>component when an error occurs. This is an After variable and it returns a string. This<br>variable functions only if the Die on error checkbox is<br>cleared, if the component has this checkbox.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from<br>it.<br><br>For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is normally an end component of a Job and always<br>needs an input link. |
| Prerequisites | Before starting, ensure that you have met the Loopback IP prerequisites expected by your<br>database.<br><br>For further information about how to install a Hadoop distribution, see the manuals<br>corresponding to the Hadoop distribution you are using. |