Configuring Looker to use a Data Virtuality driver (Looker 5.14+)

(Carter Moar) #1

Starting in Looker 5.14 you will need to configure a Data Virtuality driver. These instructions describe that process, assuming use of a startup script similar to the examples provided here.

At a high level, you will need to acquire a Data Virtuality driver JAR, include it as part of the startup process, and add an option to tell Looker to access it.

Installing the driver

1. Move the driver JAR to a subdirectory.

For example:

# log in as the looker user
cd ~/looker
mkdir ~/looker/custom_jdbc_drivers
mv ~/datavirtuality-jdbc.jar  ~/looker/custom_jdbc_drivers/datavirtuality-jdbc.jar

2. Create a configuration file

In the ~/looker directory, create a configuration file if one does not exist to tell Looker to use the new driver.

For example:

vim ~/looker/custom_jdbc_config.yml

and add the following

- name: datavirtuality
  file_name: datavirtuality/custom_jdbc_drivers/datavirtuality-jdbc.jar
  module_path: com.datavirtuality.dv.jdbc.Driver

3. Tell Looker to use the new driver

If you’re already using a lookerstart.cfg file, just add another startup option to that. If not you can add it directly to your startup script or create one (recommended).

vim lookerstart.cfg

and add the --use-custom-jdbc-config to the list of LOOKERARGS environment variable. Make sure to leave any other configs that are set there.


4. Restart Looker

./looker restart

Looker 5.14 Extended Support Release Notes
Looker 5.14 Release Notes
(Alison) #2

@cutler - What does this driver do? Trying to determine if it’s required or nice to have.

(Carter Moar) #3

The driver is what Looker uses to connect to Data Virtuality, so if you’re not using that then it is not necessary. If you have a Data Virtuality connection, these steps are absolutely required.

We should have already performed this for Looker-hosted instances with Data Virtuality connections and reached out to those who host themselves. Please let us know if we missed someone!