# tHBaseConfiguration properties for Apache Spark Batch

These properties are used to configure tHBaseConfiguration running in the Spark Batch Job framework.

The Spark Batch tHBaseConfiguration component belongs to the Storage and the Databases families.

The component in this framework is available in all subscription-based Talend products with Big Data and 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. |
| HBase version | Select the HBase 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<br>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. |
| HBase parameters | 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. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is used with no need to be connected to other<br>components.<br><br>You must drop tHBaseConfiguration along with the<br>HBase-related subJob to be run in the same Job so that the configuration is used by the<br>whole Job at runtime.<br><br>This component, along with the Spark Batch component Palette it belongs to,<br>appears only when you are creating a Spark Batch Job.<br><br>Note that in this documentation, unless otherwise explicitly stated, a<br>scenario presents only Standard Jobs, that is to<br>say traditional<br>Talend<br>data integration Jobs. |
| 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. |
| Spark Connection | In the Spark<br>Configuration tab in the Run<br>view, define the connection to a given Spark cluster for the whole Job. In<br>addition, since the Job expects its dependent jar files for execution, you must<br>specify the directory in the file system to which these jar files are<br>transferred so that Spark can access these files:<br><br><ul> <li> <span>Yarn mode</span> (Yarn client or Yarn cluster): <p>When using on-premises distributions, use                                        the configuration component corresponding to the file system                                        your cluster is using. Typically, this system is HDFS and so                                        use <a href="https://help.qlik.com/talend/r/en-US/8.0/components/hdfs/thdfsconfiguration">tHDFSConfiguration</a>.</p> <p>Actually, this component is relevant with the traditional on-premises                            Hadoop distributions only.</p> </li> <li> <p> <span>Standalone mode</span>: use the                            configuration component corresponding to the file system your cluster is                            using, such as <a href="https://help.qlik.com/talend/r/en-US/8.0/components/hdfs/thdfsconfiguration-properties-for-apache-spark-batch">tHDFSConfiguration Apache Spark Batch</a> or <a href="https://help.qlik.com/talend/r/en-US/8.0/components/amazon-s3/ts3configuration-properties-for-apache-spark-batch">tS3Configuration Apache Spark Batch</a>.</p> <p>If you are using Databricks without any configuration component present                            in your Job, your business data is written directly in DBFS (Databricks                            Filesystem).</p> </li> </ul><br><br>This connection is effective on a per-Job basis. |