Before configuring Looker to work with Teradata, you must install the
hash_md5 user-defined function (UDF) on your Teradata server. You can find instructions for installing the UDF here.
To use Looker with Teradata you will need to configure a Teradata driver. These instructions describe that process, assuming use of a startup script similar to the examples provided here.
To install the driver, you will need to acquire two Teradata files, include them as part of the startup process, and add an option to tell Looker to access the driver.
Installing the Driver
To install the Teradata driver:
Move the JARs to a subdirectory. For example:
# log in as the looker user mkdir -p ~/looker/custom_jdbc_drivers/teradata_driver mv ~/terajdbc4.jar ~/looker/custom_jdbc_drivers/teradata_driver/ mv ~/tdgssconfig.jar ~/looker/custom_jdbc_drivers/teradata_driver/
Create a configuration file.
Create a configuration file for the new driver, if one does not already exist in the
In your configuration file, add the following:
- name: teradata dir_name: teradata_driver module_path: com.teradata.jdbc.TeraDriver
Configure Looker to use the new driver.
If you are using a
lookerstart.cfgfile, add another startup option to the
If you are not using
lookerstart.cfg, add the startup option to your startup script or create a new startup script.
Then add the
--use-custom-jdbc-configstartup option to the list of
LOOKERARGSenvironment variables. Make sure to leave any other configurations that are set there.
Looker’s ability to provide some features depends on whether the database dialect supports them.
In the current Looker release, Teradata supports the following Looker features: