a547c523c2
Previously, when we loaded the next version of the table, we would block all reads with a write lock. Now, we only do that if `read_consistency_interval=0`. Otherwise, we load the next version asynchronously in the background. This should mean that `read_consistency_interval > 0` won't have a meaningful impact on latency. Along with this change, I felt it was safe to change the default consistency interval to 5 seconds. The current default is `None`, which means we will **never** check for a new version by default. I think that default is contrary to most users expectations.
1.7 KiB
@lancedb/lancedb • Docs
@lancedb/lancedb / ConnectionOptions
Interface: ConnectionOptions
Properties
apiKey?
optional apiKey: string;
(For LanceDB cloud only): the API key to use with LanceDB Cloud.
Can also be set via the environment variable LANCEDB_API_KEY.
clientConfig?
optional clientConfig: ClientConfig;
(For LanceDB cloud only): configuration for the remote HTTP client.
hostOverride?
optional hostOverride: string;
(For LanceDB cloud only): the host to use for LanceDB cloud. Used for testing purposes.
readConsistencyInterval?
optional readConsistencyInterval: null | number;
(For LanceDB OSS only): 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.
region?
optional region: string;
(For LanceDB cloud only): the region to use for LanceDB cloud. Defaults to 'us-east-1'.
storageOptions?
optional storageOptions: Record<string, string>;
(For LanceDB OSS only): configuration for object storage.
The available options are described at https://lancedb.github.io/lancedb/guides/storage/