Creating the Data Source Name
This section describes how to edit the DSN configuration and then authenticate and connect to Apache Impala APIs.
DSN Configuration
You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the installation process creates a both a user DSN and a system DSN, as described in Installing the Connector.
Note: The connector stores connection information in the Windows registry. To ensure that the connector can write to the registry, either run Power BI as an administrator or use a User DSN for your connection instead of a System DSN.
User DSN
Complete the following steps to edit the DSN configuration:
- Select Start > Search, and enter ODBC Data Sources in the Search box.
- Choose the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).
- Select the system data source and click Configure.
- Edit the information on the Connection tab and click OK.
System DSN
Configure the system DSN the same way as the user DSN, except you will need to switch to the System DSN tab before performing Step 3.
Connecting to Apache Impala
In order to connect to Apache Impala, set the following:
- Server: The name or network address of the SQL Server instance.
- Port: The port for the connection to the Impala Server instance.
- ProtocolVersion: The Thrift protocol version to use when connecting to the Impala server.
- Database (optional): A default database to use when one is not supplied in the SQL query. This enables using table names without having to specify database.tablename in the query.
- Pagesize (optional): The number of results to pull per page from Apache Impala when selecting data.
- QueryPassthrough (optional): Indicates if the query should be passed to Impala as-is.
- UseSSL (optional): Set this to enable TLS/SSL.
When QueryPassthrough is set to false (default), the CData ADO.NET Provider for Apache Impala will attempt to modify the query to conform to Impala required format.
Authenticating to Apache Impala
There are several ways to authenticate to Apache Impala including:
- NoSasl
- LDAP
- Kerberos
NoSasl
When using NoSasl, no authentication is performed. It is used when you are connecting to a server from a trusted location such as a test machine on your local network. By default, NoSasl is as the default AuthScheme, so no additional connection properties need to be set.
LDAP
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.
Kerberos
Set the AuthScheme property to Kerberos. Please see Using Kerberos for details about how to authenticate with Kerberos.