Google Cloud Storage (GCS)
Dremio allows for integration with environments using the Google Cloud Storage (GCS) web service for storing data. Configuration of this source allows for direct access to GCS data through the Dremio interface.
The following options are available from the General tab.
|Name||A name to identify the data source in Dremio.|
|Google Project ID||The specific ID for your GCS project. This can be found in the Project info pane at the top-left of your screen when at the Home page.|
|Service Account Keys||The most common method of integrating Dremio with GCS is through the creation of a service account key. When this option is selected, you need to provide values for the Client Email, Client ID, Private Key ID, and Private Key fields.|
.To obtain a service account key to fill in these fields, follow these steps.
|Automatic/Service Account||Select this option if you are currently running Dremio on a Google Compute instance. Dremio will then use the active service account for your account and does not require any additional information to integrate with your data.|
|Client Email||The email address associated with the GCS service account. This is only required when the Service Account Keys radio button is selected.|
|Client ID||The client ID for your key pair. The value is found by following the steps below to create a service account key. This is only required when the Service Account Keys radio button is selected.|
|Private Key ID||The key ID for your key pair. The value is found by following the steps below to create a service account key. This is only required when the Service Account Keys radio button is selected.|
|Private Key||The private key for your key pair. The value is found by following the steps below to create a service account key. This is only required when the Service Account Keys radio button is selected.|
Creating Service Account Keys
In order to use Dremio to access your Google Cloud Storage source, you need to first identify the service account. This is done by creating public/private key pairs. When creating service account keys, the public portion is stored on Google Cloud, while the private portion is made available to you for entry on Dremio.
The steps below outline the most simple method of creating a service account key.
- From the Google Cloud Console, navigate to the Service Accounts page.
- Select the desired project.
- Click on the email address of the service account that you'll be creating a key for.
- Click on the Keys tab.
- Click the Add Key drop-down menu and then select Create new key.
- Select JSON as the Key Type and then click Create.
Your browser then downloads a service account key file. It should look similar to the example below:Example service account key file
"private_key": "-----BEGIN PRIVATE KEY-----\nprivate-key\n-----END PRIVATE KEY-----\n",
Copy and paste each value from this file to the corresponding fields on the Dremio interface.
For additional methods of creating a key (e.g.,
gcloud tool, REST APIs, etc.), view Google's documentation.
Advanced Options Tab
The following settings control more advanced functionalities in Dremio.
|Enable asynchronous access when possible||Allows for multiple queries simultaneously rather than waiting for a single query to complete before new tasks are performed.|
|Root Path||The root path for the GCS source.|
|Properties||Additional connection properties, consisting of the property and its specified value.|
|Whitelisted buckets||A list of buckets to whitelist, or allow access to.|
|Enable local caching when possible||Dremio creates caches locally of any data used from the source.|
|Max percent of total available cache space to use when possible||Sets the allowable amount of local caching, based on percentage. Only the percent specified of the cached files will be stored locally. By default, this is set to 100.|
Reflection Refresh Tab
This tab controls the frequency of reflection refreshes or the timespan for expiration for any queries performed using this data source.
|Never refresh||Prevents any query reflections associated with this source from refreshing.|
|Refresh every||Sets the time interval by which reflections for this source are refreshed. This may be set to hours, days, and weeks.|
|Never expire||Prevents any query reflections associated with this source from expiring.|
|Expire after||Sets the time after a reflection is created that it then expires and can no longer be used for queries. This may be set to hours, days, and weeks.|
This tab offers settings that control how dataset details are fetched and refreshed.
|Remove dataset definitions if underlying data is unavailable||If this box is not checked and the underlying files under a folder are removed or the folder/source is not accessible, Dremio does not remove the dataset definitions. This option is useful in cases when files are temporarily deleted and put back in place with new sets of files.|
|Automatically format files into tables when users issue queries||If this box is checked and a query runs against the un-promoted table/folder, Dremio automatically promotes using default options. If you have CSV files, especially with non-default options, it might be useful to not check this box.|
|Dataset Discovery||Specifies the refresh interval for top-level source object names, such as database and table names. This is a lightweight operation.|
Fetch every. Specifies the time interval by which Dremio fetches object names. This can be set by minutes, hours, days, and weeks.
|Dataset Details||Specifies the metadata that Dremio needs for query planing, such as information regarding fields, types, shards, statistics, and locality.|
Fetch mode. Restricts when metadata is retrieved.
Only Queried Datasets. Dremio updates metadata details for previously-queried objects in a source. This mode increases query performance as it requires less work to be done at query time for these datasets.
All Datasets (deprecated). Dremio updates the details for all datasets in a source. This mode increases query performance as less work is needed to be done at the time of query.
Fetch every. Specifies the time interval by which metadata is fetched. This can be set by minutes, hours, days, and weeks.
Expire after. Specifies the timespan for when dataset details expire after a dataset is queried. This can be set by minutes, hours, days, and weeks.
From this tab, administrators may control access to the data source on a user-by-user or group-by-group basis.