> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/hbase-input-cp-main-page/select-an-engine-hbase-input/using-hbase-input-step-on-the-pentaho-engine-cp/options-hbase-input-reuse/configure-query-tab-hbase-input-reuse.md). # Configure query tab Before a value can be read from HBase, you must specify the type and column family of the value, and the type of the table key. You must define a mapping to use a source table. You can output some or all of the fields defined in the mapping. Rows from the table may be deleted to select a subset of the fields. Clearing all rows from the table indicates that all fields defined in the mapping should be output. This tab contains connection details and basic query information. You can configure a connection by using the Hadoop cluster properties, or by using an `hbase-site.xmland` (an optional) `hbase-default.xml` configuration file. ![Configure query tab](/files/8sANYBNKW6MS2hZNQQzi) This tab includes the following fields: | Option | Description | | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Hadoop Cluster** |

Click the Hadoop Cluster drop-down menu to select an existing Hadoop cluster configuration.

Refer to Connecting to a Hadoop cluster with the PDI client for information on creating and editing a Hadoop cluster.

| | **URL to hbase-site.xml** | Specify the address of the `hbase-site.xml` file by entering its path or clicking **Browse**. | | **URL to hbase-default.xml** | Specify the address of the `hbase-default.xml` file by entering its path or clicking **Browse**. | | **HBase table name** | Select the name of the source HBase table you want to read. | | **Get mapped table names** (button) | Click to retrieve a list of all existing table names for the **HBase table name** field. Only table names that have been mapped are retrieved. If you enter the `namespace:tablename` in the **HBase table name** field, then click **Get mapped table names**, only the mapped table names in that namespace display. If you do not enter a namespace, all HBase tables across all namespaces are displayed. See [Namespaces](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/hbase-input-cp-main-page/select-an-engine-hbase-input/using-hbase-input-step-on-the-pentaho-engine-cp/namespaces.md). | | **Mapping name** | A mapping you can use to decode and interpret column values. Click **Get mappings for the specified table** to populate the drop-down list of available mappings. | | **Store mapping info in step meta data** | Select this option to store mapping information in the step's metadata instead of loading it from HBase at runtime. | | **Start key value (inclusive) for table scan** | Specifies the starting key value of a partial scan, including the value entered. | | **Stop key value (exclusing) for table scan** | Specifies the stopping key value of a partial scan, excluding the value entered. The start key and stop key fields may be left blank. If the stop key field is left blank, then all rows beginning with and including the start key will be returned. | | **Scanner row cache size** | The number of rows to cache each time a fetch request is made. See the [Performance considerations](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/hbase-input-cp-main-page/select-an-engine-hbase-input/using-hbase-input-step-on-the-pentaho-engine-cp/performance-considerations-hbase-input-reuse.md) section below for more information. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/hbase-input-cp-main-page/select-an-engine-hbase-input/using-hbase-input-step-on-the-pentaho-engine-cp/options-hbase-input-reuse/configure-query-tab-hbase-input-reuse.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.