feat(java): support cache backend register and switch - #8446
Merged
Conversation
yanghua
marked this pull request as ready for review
August 11, 2026 00:29
Contributor
There was a problem hiding this comment.
✅ Gate recommendation: approve.
This closes the Java binding gap through the existing native URI/config registry while preserving independent size and default behavior for each cache tier. The typed immutable configuration keeps Java thin and leaves backend parsing and validation in the Rust core.
Xuanwo
approved these changes
Aug 11, 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.
Summary
Add Java APIs to select registered native cache backends using either
backend URIs or structured CacheBackendConfig.
Allow index and metadata caches to switch backends independently while
preserving existing size-based and default configurations.
Bridge backend configuration through JNI to Lance’s cache registry, with
validation and tests for conflicting or invalid settings.