Google Cloud Storage file system support#
Trino includes a native implementation to access Google Cloud Storage (GCS) with a catalog using the Delta Lake, Hive, Hudi, or Iceberg connectors.
Enable the native implementation with fs.native-gcs.enabled=true
in your
catalog properties file.
General configuration#
Use the following properties to configure general aspects of Google Cloud Storage file system support:
Property |
Description |
---|---|
|
Activate the native implementation for Google Cloud Storage support.
Defaults to |
|
Identifier for the project on Google Cloud Storage. |
|
Optional URL for the Google Cloud Storage endpoint. Configure this property
if your storage is accessed using a custom URL, for example
|
|
Maximum number of RPC attempts. Defaults to 20. |
|
Scale factor for RPC retry delays. Defaults to 3. |
|
Total time duration limit for RPC call retries.
Defaults to |
|
Minimum delay duration between RPC retries. Defaults
to |
|
Maximum delay duration between RPC retries. Defaults
to |
|
Minimum data size for blocks read per RPC. Defaults
to |
|
Minimum data size for blocks written per RPC. The
Defaults to |
|
Maximum number of blobs to return per page. Defaults to 100. |
|
Number of blobs to delete per batch. Defaults to 100. Recommended batch size is 100. |
|
Specify the application identifier appended to the |
Authentication#
Use one of the following properties to configure the authentication to Google Cloud Storage:
Property |
Description |
---|---|
|
Flag to set usage of a client-provided OAuth 2.0 token to access Google
Cloud Storage. Defaults to |
|
Your Google Cloud service account key in JSON format. Not to be set together
with |
|
Path to the JSON file on each node that contains your Google Cloud Platform
service account key. Not to be set together with |
Migration from legacy Google Cloud Storage file system#
Trino includes legacy Google Cloud Storage support to use with a catalog using the Delta Lake, Hive, Hudi, or Iceberg connectors. Upgrading existing deployments to the current native implementation is recommended. Legacy support is deprecated and will be removed.
To migrate a catalog to use the native file system implementation for Google Cloud Storage, make the following edits to your catalog configuration:
Add the
fs.native-gcs.enabled=true
catalog configuration property.Refer to the following table to rename your existing legacy catalog configuration properties to the corresponding native configuration properties. Supported configuration values are identical unless otherwise noted.
Legacy property |
Native property |
Notes |
---|---|---|
|
|
|
|
|
Also see |