Unable to Connect to DataStax Enterprise

Published: 30 Aug 2013
Last Modified Date: 18 Jul 2017


Unable to connect to DataStax Enterprise.


  • Tableau Desktop
  • DataStax Enterprise
  • Cassandra ODBC driver


Use one of the following workarounds.

Option 1: Connect using the supported driver

If you are using a DataStax Enterprise version between 2.2 and 4.5, connect using the named DataStax connector and the DataStax ODBC Driver for Hive (32-bit). This driver is available for download from the Tableau Drivers & Activation page. Note that the Hive layer is packaged with DataStax Enterprise and may need to be separately configured.

If you are using DataStax Enterprise 5.0 or later, connect using the SparkSQL connector and SparkSQL driver. Like Hive, Spark may need to be separately configured on the DataStax Enterprise cluster.

Please refer to DataStax documentation and support for assistance configuring Hive or Spark for your cluster.

Option 2: Connect using Cassandra and Other Databases (ODBC) connection

If you must use the Cassandra driver, it may be possible to connect to DataStax using the Other Databases (ODBC) data connection.

Warning: Although it may be possible to connect to DataStax using the Cassandra driver and the Other Databases (ODBC) data connection, success often varies and full compatibility with Tableau features cannot be guaranteed. Refer to the following resources for additional information about the capabilities and limitations of connecting to unsupported data sources via the general-purpose ODBC:

Option 3: Create an extract using the Tableau Data Extract API

Use the Tableau Data Extract API, which will allow you to connect to a data source that is not currently supported and extract data into a Tableau Data Extract (.tde) file. You can connect to the data extract from Tableau Desktop or publish the extract to Tableau Server. For more information, see Tableau Data Extract API in Tableau Help.


Connecting directly to Cassandra tables using the DataStax ODBC is not supported.
Did this article resolve the issue?