This is the Tableau Connector for Startree Pinot.
We are working on making this connector available in the Tableau Exchange. For now, the connector can be installed and used as follows.
-
Pinot setup requires JDK 11 and Maven 3.6
-
Download the driver jars. When using Pinot 1.0.0, the driver versions below will be needed
- async-http-client-2.12.3.jar
- calcite-core-1.30.0.jar
- pinot-jdbc-client-1.0.0-hotfix-shaded.jar
-
Copy the driver to the Tableau drivers directory
- On Mac:
~/Library/Tableau/Drivers/ - On Windows:
C:\Program Files\Tableau\Drivers
- On Mac:
-
Fork this repository
-
Exec
mvn packagein this directory to build the connector. The.tacofile will be in thetargetsubdirectory. -
Copy the
.tacoto the connectors directory- On Mac:
~/Library/Tableau/Connectors/ - On Windows:
C:\Users\[user]\Documents\My Tableau Repository\Connectors
- On Mac:
-
Launch Tableau Desktop with connector signature verification disabled.
- On Mac:
/Applications/Tableau\ Desktop\ <version>.app/Contents/MacOS/Tableau -DDisableVerifyConnectorPluginSignature=true - On Windows:
tableau.exe -DConnectPluginsPath=C:\tableau_connector
- On Mac:
-
Select the connector from installed connectors
Maven is configured to sign the .taco file during the package stage.
Signing requires the following maven properties
- taco.signing.keystore - The path to the
.jksfile containing the code-signing certificate (defaults totaco.jks)- NOTE: the
taco.jksin this directory is just a placeholder. It DOES NOT contain a valid certificate and must be replaced with a valid.jksfile when actually signing the.tacofor distribution
- NOTE: the
- taco.signing.alias - The alias for the keystore entry that contains the private key needed to generate the signature (defaults to
alias) - taco.signing.storepass - The password for the keystore (defaults to
storepass) - taco.signing.keypass - The password for the keystore entry (defaults to empty)
For example, to build a signed .taco file
mvn package -Dtaco.signing.keystore=taco.jks -Dtaco.signing.alias=pinotkeyalias -Dtaco.signing.storepass=tacostorepass -Dtaco.signing.keypass=tacokeypass
To automate the building/signing of the .taco secrets could be used along with a github action to run the build with the properties configured from values stored in the secrets.


