> 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/namespaces.md).

# Namespaces

You can use namespaces in the **HBase table name** field to create a logical grouping of your tables. For example, you can use one namespace for your development environment and another namespace for your production environment.

You must create a namespace before you can write to it. If you do not enter a namespace when creating a mapping, Pentaho uses the default namespace which is named `default`. See <https://hbase.apache.org/book.html#_namespace> for information on creating namespaces.

You can also use a variable for a namespace, which provides an easy way to move a transformation from your development environment to your production environment without having to change anything except the parameters. You can use transformation-level or system-level variables for a namespace.

The variable format is `${nsvarname}:`

**Note:** Every namespace has a `pentaho_mappings` table that stores the mappings metadata for the columns. This table is created automatically when you create mappings.


---

# 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/namespaces.md?ask=<question>&goal=<endgoal>
```

`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.