Skip to main content
GuideServerConfigure and deploy Tabsdata servers on your machine.TutorialsConfigure data integration workflows within a running Tabsdata server.API ReferenceCLI ReferenceRelease Notes
Version: 2.3.0

Object Store Options

Several connectors read or write cloud object storage through an object store client. Keys that start with obstore. configure that client. Set them where the connector takes its other settings: conn_cfg on the connection for the file connectors, and cfg on the staging location for ClickHouse, StarRocks and Druid.

Where the keys apply​

ConnectorSet withWhat the keys configure
Amazon S3, Google Cloud Storage, Azure Blob Storageconn_cfg on the connectionReads and writes
ClickHousecfg on the staging locationThe staging upload, the address ClickHouse reads the files from, and the cleanup
StarRockscfg on the staging locationThe staging upload. StarRocks reads the files through its own path, which the keys do not change
Druidcfg on the staging locationThe staging upload. The ingestion input source does not use them

On the file connectors, a key in conn_cfg overrides the matching credential in the connection. The explorer ignores these keys.

Keys by provider​

ProviderKeys
Amazon S3access_key_id, secret_access_key, session_token, region, endpoint, virtual_hosted_style_request, allow_http, anonymous, skip_signature
Azure Blob Storageaccount_name, account_key, sas_token, endpoint, allow_http
Google Cloud Storageservice_account_key, service_account, allow_http

service_account is the path to a key file on the Tabsdata server. Raw option names with the aws_, azure_ or google_ prefix are accepted as well.

For example, to point an S3 connection at a MinIO server:

conn_cfg:
obstore.endpoint: 'http://minio.internal:9000'

On ClickHouse, an unknown obstore.* key fails the write.