(warning) The Data Prep (Paxata) documentation is now available on the DataRobot public documentation site. See the Data Prep section for user documentation and connector information. After the 2021.2 SP1 release, the content on this site will be removed and replaced with a link to the DataRobot public documentation site.

Tableau.Hyper Connector Documentation

User Persona: Paxata User - Paxata Admin - Data Source Admin


*Note: This document covers all configuration fields available during Connector setup. Some fields may have already been filled out by your Admin at an earlier step of configuration and may not be visible to you. For more information on Paxata’s Connector Framework, please see here.

Also: Your Admin may have named this Connector something else in the list of Data Sources.

Configuring Paxata

This connector allows you to connect to Tableau as an export destination. The following fields are used to define the connection parameters.

General

  • Name: Name of the data source as it will appear to users in the UI.
  • Description: Description of the data source as it will appear to users in the UI.

Something to consider: You may connect Paxata to multiple Tableau instances and having a descriptive name can be a big help to users in identifying the appropriate data source. If you are a Paxata SaaS customer, please inform Paxata DevOps how you would like this set.

Tableau Configuration

  • Tableau Server URL: An http or https URL where the Tableau Server is running. Include port if necessary. For Tableau Online, the URL must contain the pod name, such as 10az, 10ay, or us-east-1.
  • Site: Tableau site in which Paxata will publish a data source.
  • Project: Tableau project in which Paxata will publish a data source.
  • Overwrite Tableau Data Source: Overwrite a data source that has the same name, if one already exists.

Tableau Credentials

  • Username: Username or email address for authenticating with Tableau.
  • Password: Password for authenticating with Tableau.

Web Proxy

If you connect to Tableau through a proxy server, these fields define the proxy details.

  • Web Proxy: 'None' if no proxy is required or 'Proxied' if the connection to the Tableau REST Endpoint should be made via a proxy server. If a web proxy server is required, the following fields are required to enable a proxied connection.
  • Proxy host: The host name or IP address of the web proxy server.
  • Proxy port: The port on the proxy server for Data Source.
  • Proxy username: The username for the proxy server.
  • Proxy password: The password for the proxy server.
    *Leave username & password blank for an unauthenticated proxy connection.

Data Export Information

Via Browsing

Files are published into the specified Site and Project defined in the Tableau Connector/Datasource configuration.

No directories will be visible in the browsing UI. Click the ‘Select’ button in the export view to export into the specified Site and Project.

Note that AnswerSets are converted to Tableau Hyper Extract (.hyper) files and then published into the specified Site and Project you define here.

Via SQL Query

Not supported.

Technical Specs

Deployment Scenarios

The Tableau Hyper connector writes .hyper files using native libraries from the Tableau SDK. There are two supported deployment scenarios that allow you to use these native libraries:

  1. Use the native libraries that are bundled in the connector. This is the recommended approach.
  2. Install the Tableau SDK on the host system and remove the native libraries that are extracted from the connector zip.

If you need additional information or help installing the SDK for the Tableau Hyper Connector, please reach out to your Customer Success representative.

FAQ/Troubleshooting/Common Issues

  • Why are there two Tableau Connectors and what’s the difference?
    • Tableau “.tde” is an older extract type and was implemented with version 1.0 of Tableau’s extract API. The Tableau “.hyper” Connector is newer and is based on version 2.0 of Tableau’s extract API. We built the “.hyper” Connector as a net-new Connector so both Connectors could coexist in an account enabling customers who have many versions of Tableau running to choose the best Connector for each instance of Tableau.