Connection URIs
Connect to LanceDB has examples for each connection type.
A connection to object storage still uses the embedded library: your process
reads and writes the bucket directly. Enterprise runs operations remotely and
manages the supporting compute and maintenance.
Connect to Enterprise
Replace the placeholders with the database URI, key, region and endpoint provided by your administrator.
Use your deployment’s region rather than relying on the
us-east-1 default.
For application code, load credentials from environment variables or a secrets
manager. See Authentication for OAuth and
SQL for the separate SQL connection settings.
Storage options
For LanceDB Embedded tables in object storage,storage_options configures credentials,
endpoints and options for new tables. This example enables stable row IDs for
tables created through the connection:
Read consistency
For LanceDB Embedded connections,read_consistency_interval controls how often reads check
for table versions committed by other writers. For example, check at most once
every five seconds:
Database operations
The connection provides methods to create, open, list and drop tables.
Use the namespace and pagination options documented in
Namespaces when working outside the root namespace
or listing a large catalog. Tables covers table schemas,
versions and lifecycle operations.
Async connections
Python’sconnect_async returns an AsyncConnection. Await its operations
when working in an asynchronous application:
Privileges
A database’sOWNERSHIP, USAGE and CREATE_NAMESPACE are granted through
the REST ACL API or SQL GRANT/REVOKE: