- Hostname and path of your Databricks cluster
- an Access token that has permissions to run queries there
You may also need to ensure that your firewall accepts requests from the following IP addresses:
Once you hit Connect you will see your connection details including a full list of tables accessible with this connection.
The most common issue common issue when connecting to a Databricks cluster is that the warehouse is unresponsive if it has stopped due to inactivity. Count's connecting and querying logic will retry every 10 seconds for 3 minutes. If Count is still unable to connect to your cluster after this time, a 503 error will return. Ensure that your warehouse is running and available to accept connections from the Count IP addresses (see above) and retry the connection in Count.
The BigInt data type in Databricks can accommodate integers in the range
2^63 -1. Due to a limitation in the Databricks client, Count can accommodate a reduced range of
2^53 -1for this data type. Values outside of this reduced range will be displayed as
Count uses a reduced parse to determine which cells are referenced in your SQL statements. Databrick's SELECT statement and querying syntax is more flexible than those of other databases. As a result, there is an unresolvable ambiguity in Count's reduced parse for statements of the form
SELECT * FROM VALUES 1, 2, 3
Running a SQL statement similar to this will result in an error similar to "Unexpected number", "Unexpected literal", etc. The workaround for this issue is to parenthetise the row values in the
SELECT * FROM VALUES (1), (2), (3)