Enterprise Azure storage_options + sync LanceDB stack to data plane#16
Open
ryan-haynes wants to merge 1 commit into
Open
Enterprise Azure storage_options + sync LanceDB stack to data plane#16ryan-haynes wants to merge 1 commit into
ryan-haynes wants to merge 1 commit into
Conversation
…lane Two changes to run the quickstart CLIs against an enterprise cluster on Azure and to match the current data-plane build: - config.py: add azure_account_name/azure_account_key fields and an Azure branch in storage_options() (Azure takes precedence, else S3, else None). Enterprise clients write Lance fragments directly to object storage, and the account-less az://<container> root URI needs the storage account named explicitly. The S3 path is unchanged. - pyproject.toml/uv.lock: bump geneva 0.13.0b18 -> 0.13.0b30, lancedb 0.33.1b2 -> 0.34.0b5, pylance 8.0.0b16 -> >=9.0.0b15 to match the deployed cluster's geneva 0.13.0b30 build. The older pylance/lancedb spoke a different namespace API, so add_columns succeeded but backfill_column returned "column not found" / declare_table 500s. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
justinrmiller
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two changes needed to run the quickstart CLIs against an enterprise LanceDB cluster on Azure, and to keep the client's LanceDB stack in lockstep with the deployed data plane.
config.py— Azurestorage_optionsazure_account_name/azure_account_keyconfig fields (read fromconfig.yaml).storage_options(): Azure (account name + key) takes precedence, else S3-compatible (all four creds), elseNone.az://<container>root URI has no way to resolve the storage account, so it must be named explicitly here. The S3 path is unchanged.pyproject.toml/uv.lock— LanceDB stack bumpgeneva0.13.0b18→0.13.0b30lancedb0.33.1b2→0.34.0b5pylance8.0.0b16→>=9.0.0b15geneva 0.13.0b30build (the sophonlancedb_integtestpins). The olderpylance/lancedbspoke a different namespace API, soadd_columnswould succeed butbackfill_columnreturned"column not found"anddeclare_table500'd against the current server.Testing
Validated end-to-end against enterprise clusters on both clouds:
ingest-images→lightweightbackfill (file_size + dimensions) commits successfully.Notes for reviewer
config.yamlis gitignored (it holds per-user creds) and is not part of this PR.