Creating Looker Configuration

After creating a connection to AtScale you should set the Looker configuration properties in AtScale. Optionally, you can also specify the connection to be used for queries that do not contain a FROM clause.

Before you begin

  • Ensure there is at least one AtScale sample project in your instance.
  • Ensure a connection is created. For details, see Creating Looker Connection.
  • Ensure you have Looker-enabled license, and you know how to manage licenses in AtScale. For details, see Viewing and Updating Licenses.

Creating Looker configuration

Perform all of the following steps in AtScale:

  1. Import your Looker-enabled license file, and then restart your Engine.

  2. Choose Settings and go to Integrations and Services.

  3. Choose the Create Looker Configuration button and fill in the fields as follows:

    • CONFIGURATION NAME: The name of Looker configuration, which should be unique. If multiple Looker configurations exist, this value is used to distinguish between them in the user interface.

    • CONNECTION NAME: The connection name you set for the AtScale server when configuring the Looker "Connection Settings". This value is used to identify the Connection ID in the generated LookML.

    • LOOKER REPO PATH: when using Git integration, enter here the URL of the Git repository, for example

      For more information, see Using LookML files in Looker.



    • REGEX FILTER FOR ATSCALE PROJECTS TO BE EXPORTED (COMMA DELIMITED): This regex is used to determine which Projects can be exported to Looker. If this expression matches the project name, then the Publish Wizard will display options to publish the project to the Looker Git Repository. For example, you can use .* for all projects.

  4. Choose Update to save the Looker configuration.

Setting a connection for queries that do not contain a FROM clause

Some queries from Looker don't specify a FROM clause. You can set which connection to be used for such queries in the following way:

  1. Go to Setting > Data Warehouses and choose the EDIT button for the one to be used.
  2. Copy the value of the EXTERNAL CONNECTION ID field, and then exit the warehouse editing dialog.
  3. Go to Settings > Engine.
  4. Locate the QUERY.NOFROM.CONNECTIONID setting.
  5. Enter the value you copied in step 2.
  6. Choose SAVE SETTINGS at the bottom of the list of settings.

In case such a connection is not set, or is set to an invalid name, the first connection from the first cube in the project will be used.

For more information, see Changing Advanced Engine Settings and Adding Data Warehouses.