@lancedb/lancedb • Docs
@lancedb/lancedb / ConnectionOptions
Interface: ConnectionOptions¶
Properties¶
apiKey?¶
(For LanceDB cloud only): the API key to use with LanceDB Cloud.
Can also be set via the environment variable LANCEDB_API_KEY.
clientConfig?¶
(For LanceDB cloud only): configuration for the remote HTTP client.
hostOverride?¶
(For LanceDB cloud only): the host to use for LanceDB cloud. Used for testing purposes.
manifestEnabled?¶
(For LanceDB OSS only): use directory namespace manifests as the source of truth for table metadata. Existing directory-listed root tables are migrated into the manifest on access.
namespaceClientProperties?¶
(For LanceDB OSS only): extra properties for the backing namespace client used by manifest-enabled native connections.
readConsistencyInterval?¶
The interval, in seconds, at which to check for updates to the table from other processes. If None, then consistency is not checked. For performance reasons, this is the default. For strong consistency, set this to zero seconds. Then every read will check for updates from other processes. As a compromise, you can set this to a non-zero value for eventual consistency. If more than that interval has passed since the last check, then the table will be checked for updates. Note: this consistency only applies to read operations. Write operations are always consistent.
Stronger consistency is not free. The smaller the interval, the more often each read pays the cost of checking for updates against object storage, raising per-read latency and cost.
region?¶
(For LanceDB cloud only): the region to use for LanceDB cloud. Defaults to 'us-east-1'.
session?¶
(For LanceDB OSS only): the session to use for this connection. Holds shared caches and other session-specific state.
storageOptions?¶
(For LanceDB OSS only): configuration for object storage.
The available options are described at https://docs.lancedb.com/storage/