[#8919] improve(lance-table): Supports object store configurations for lance table storage#9185
Merged
yuqi1129 merged 1 commit intoapache:mainfrom Nov 20, 2025
Conversation
…ons for Lance table (apache#8920) - The properties with the prefix `lance.storage.` will be used for lance table storage Fix: apache#8919 no by hand
yuqi1129
approved these changes
Nov 20, 2025
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
3 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 changes were proposed in this pull request?
This PR adds support for object store configurations for Lance tables in the generic lakehouse catalog:
lance.storage.*as a configurable property prefix at catalog, schema, and table levels for Lance table storage optionslance.storage.*prefix toGenericLakehouseCatalogPropertiesMetadata,GenericLakehouseSchemaPropertiesMetadata, andGenericLakehouseTablePropertiesMetadataLanceCatalogOperations.createTable()to extractlance.storage.*properties and pass them to Lance'sWriteParams.Builder().withStorageOptions()Refactoring: Restructured table location and storage property calculation logic in GenericLakehouseCatalogOperations
Why are the changes needed?
Lance tables need to support various object storage backends (S3, GCS, ADLS, OSS) with specific configurations like credentials, endpoints, and regions. Without this feature, users cannot configure Lance tables to work with cloud object stores, limiting Lance to local file systems only. This change enables production deployments of Lance tables on cloud storage.
Fix: #8919
Does this PR introduce any user-facing change?
Yes, users can now configure Lance table storage options using properties with the
lance.storage.prefix at catalog, schema, or table level.Properties follow precedence: table > schema > catalog.
How was this patch tested?
By hand (manual testing).