> 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-job-entries-reference-overview/bulk-load-into-databricks/options-bulk-load-into-databricks/output-tab-bulk-load-into-databricks.md).

# Output tab

Use this tab to configure the target table in Databricks. Once a connection is selected for the entry to use, the **Catalog** field is populated with the available catalogs from that Databricks connection. Once you select a catalog, the **Schema** field is populated, then when you select a Schema, the tables are populated.

![PDI Bulk load Databricks Output tab](/files/GQ1HYVrANYXFHP4y2us0)

| Field                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Database connection** | <p>Specify the Databricks database connection to the Databricks account. You can authenticate with either an access token or a username and password. The username must be the email address that you use to login to Databricks. Click <strong>Edit</strong> to revise an existing connection; click <strong>New</strong> to add a new connection.</p><p>For example:</p><p><code>jdbc:databricks\://\<server hostname>:443;HttpPath=\<HTTP path>;PWD=\<Personal Access Token></code> and <code>jdbc:databricks\://\<serverhostname>:443;HttpPath=\<HTTP path></code>. The <strong>Custom driver class name</strong> is <code>com.databricks.client.jdbc.Driver.</code></p> |
| **Catalog**             | Specify a catalog from the list of available catalogs in your Databricks connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Schema**              | Specify the schema of the target table.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Table name**          | Specify the name of the target table.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |


---

# 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-job-entries-reference-overview/bulk-load-into-databricks/options-bulk-load-into-databricks/output-tab-bulk-load-into-databricks.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.
