Starburst Documentation
Starburst Galaxy
  • Starburst Galaxy Home
  •   Get started
  •   Global features
  • Help center
  • Release notes
  • Feature release types
  • Starburst Galaxy UI
  •   Query
  •   Catalogs
  •   Catalog explorer
  •   Data products
  •   Clusters
  • Partner connect
  •   Admin
  •   Access control
  •   Cloud settings
  • Administration
  •   Security
  •   Single sign-on
  •   Troubleshooting
  • Galaxy status
  • Reference
  •   Python
  • API
  •   SQL
  •   Tutorials

    • starburst galaxy > catalogs > Druid catalogs

    Druid catalogs #

    You can use an Apache Druid® catalog to query data stored in an Apache Druid database.

    Follow these steps to begin creating a catalog for Druid:

    • In the navigation menu, select Catalogs.
    • Click Create catalog.

    • On the Select a data source pane, click the Druid icon.

      Select a data source

    • Follow the instructions in the next sections to configure your Druid connection.

    Select a cloud provider #

    The Cloud provider configuration is necessary to allow Starburst Galaxy to correctly match catalogs and clusters.

    The data source configured in a catalog, and the cluster must operate in the same cloud provider and region for performance and cost reasons.

    Select cloud provider

    Define catalog name and description #

    The Name of the catalog is visible in the Query editor and other clients. It is used to identify the catalog when writing SQL or showing the catalog and its nested schemas and tables in client applications.

    The name is displayed in the Query editor, and when running a SHOW CATALOGS command. It is used to fully qualify the name of any table in SQL queries following the catalogname.schemaname.tablename syntax. For example, you can run the following query in the sample cluster without first setting the catalog or schema context.

    SELECT * FROM tpch.sf1.nation;

    The Description is a short, optional paragraph that provides further details about the catalog. It appears in the Starburst Galaxy user interface and can help other users determine what data can be accessed with the catalog.

    Enter catalog name and description

    Configure the connection #

    The connection to the database requires username and password authentication and details to connect to the database server, typically hostname or IP address and port. The following sections detail the setup for the supported cloud providers.

    A connection to the database can be established directly, if the Starburst Galaxy IP range/CIDR is allowed to connect.

    If the database is only accessible inside the virtual private cloud (VPC) of the cloud provider, you can use an SSH tunnel with a bastion host in the VPC.

    Starburst Galaxy supports AWS PrivateLink for Druid catalogs.

    Apache Druid connection #

    To directly connect to your Druid cluster, you must provide the following details:

    • Host of broker or router: The IP address of the Druid host and its port. If there are multiple Druid brokers, connect to either a router or a specific broker, or use a load balancer with sticky sessions enabled.
    • Username: The username for the Druid instance.
    • Password: The password for the Druid instance.
    • Use TLS: Encrypts traffic in transit between Galaxy and Druid. Defaults to off.

    Test the connection #

    Once you have configured the connection details, click Test connection to confirm data access is working. If the test is successful, you can save the catalog.

    If the test fails, look over your entries in the configuration fields, correct any errors, and try again. If the test continues to fail, Galaxy provides diagnostic information that you can use to fix the data source configuration in the cloud provider system.

    Test connection

    Connect catalog #

    Click Connect catalog, and proceed to set permissions where you can grant access to certain roles.

    Set permissions #

    This optional step allows you to configure read only access to the catalog.

    Setting permissions grants all specified roles read only access to the catalog. As a result, users have read access to all contained schema, tables, and views.

    Use the following steps to assign read access to roles:

    • In the Catalog-level permissions section, toggle the Read-only catalog switch to prevent write access. For catalogs pre-set to read-only, this option is already set to Read-only catalog and disabled.
    • In the Role-level permissions section, expand the menu in the Roles with read access field.
    • Select one or more roles from the list to grant read access to.

    • Click Save access controls.

        Set permissions for read only screenshot

    Add to cluster #

    You can add your catalog to a cluster later by editing a cluster. Click Skip to proceed to the catalogs page.

    Use the following steps to add your catalog to an existing cluster or create a new cluster in the same cloud region:

    • In the Add to cluster section, expand the menu in the Select cluster field.
    • Select one or more existing clusters from the drop down menu.
    • Click Create a new cluster to create a new cluster in the same region, and add it to the cluster selection menu.

    • Click Add to cluster to view your new catalog’s configuration.

        Add to cluster

    The Pending changes to clusters dialog appears when you try to add a catalog to a running cluster.

    • In the Pending changes to cluster dialog, click Return to catalogs to edit the catalog or create a new catalog.
    • Click Go to clusters to confirm the addition of the catalog to the running cluster.

    • On the Clusters page, click the Update icon beside the running cluster, to add the catalog.

        pending changes to cluster dialog

    SQL support #

    The catalog provides read access to data and metadata in Druid. It supports the following features: