> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/bigdata/sparksql.md).

# Apache Spark

### Connecting to Spark SQL <a href="#connecting-to-spark-sql" id="connecting-to-spark-sql"></a>

Specify the following to establish a connection with Spark SQL:

* Server: Set this to the host name or IP address of the server hosting SparkSQL.
* Port: Set this to the port for the connection to the SparkSQL instance.
* TransportMode: The transport mode to use to communicate with the SparkSQL server. Accepted entries are BINARY and HTTP. BINARY is selected by default.

#### Securing Spark SQL Connections <a href="#securing-spark-sql-connections" id="securing-spark-sql-connections"></a>

To enable TLS/SSL in the provider, set UseSSL to True.

### Authenticating to Spark SQL <a href="#authenticating-to-spark-sql" id="authenticating-to-spark-sql"></a>

The service may be authenticated to using the PLAIN, LDAP, NOSASL, KERBEROS auth schemes.

#### PLAIN <a href="#plain" id="plain"></a>

To authenticate with PLAIN, set the following connection properties:

* AuthScheme: Set this to PLAIN.
* User: Set this to user to login as.
* Password: Set this to the password of the user.

To authenticate, set User and Password.

#### LDAP <a href="#ldap" id="ldap"></a>

To authenticate with LDAP, set the following connection properties:

* AuthScheme: Set this to LDAP.
* User: Set this to user to login as.
* Password: Set this to the password of the user.

To authenticate, set User, Password, and AuthScheme.

#### NOSASL <a href="#nosasl" id="nosasl"></a>

When using NOSASL, no authentication is performed. Set the following connection properties:

* AuthScheme: Set this to NOSASL.

#### Kerberos <a href="#kerberos" id="kerberos"></a>

Please see Apache HDFS connector for details on how to authenticate with Kerberos.

### Connecting to Databricks <a href="#connecting-to-databricks" id="connecting-to-databricks"></a>

To connect to a Databricks cluster, set the properties as described below. Note: The needed values can be found in your Databricks instance by navigating to 'Clusters', selecting the desired cluster, and selecting the JDBC/ODBC tab under 'Advanced Options'.

* Server: Set to the Server Hostname of your Databricks cluster.
* Port: 443
* TransportMode: HTTP
* HTTPPath: Set to the HTTP Path of your Databricks cluster.
* UseSSL: True
* AuthScheme: PLAIN
* User: Set this to user to login as
* Password: Set to your personal access token (value can be obtained by navigating to the User Settings page of your Databricks instance and selecting the Access Tokens tab).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/bigdata/sparksql.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.