-
Notifications
You must be signed in to change notification settings - Fork 767
fix: re-sort extracted JSON path values before training value-ordered indexes #7771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sohumt123
wants to merge
2
commits into
lance-format:main
Choose a base branch
from
sohumt123:fix/json-float-index-resort
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Does arrow-array's record_batch! macro support building a LargeBinary column from a Vec<&[u8]> variable in the arrow-rs version used by lance?💡 Result:
Yes, the record_batch! macro in arrow-rs supports building a LargeBinary column from a variable (such as a Vec<&[u8]>) [1][2][3]. Following recent updates to the arrow-rs library (specifically in pull request
#9522, merged in March 2026), the record_batch! macro was extended to accept both literal values and variables/expressions for array data, including support for LargeBinary types [1][4]. You can use it as follows: let large_binary_values = vec![b"some_data".as_slice]; let record_batch = record_batch!( ("my_col", LargeBinary, large_binary_values)).unwrap; In this syntax, the macro correctly handles the variable by utilizing LargeBinaryArray::from_vec [1][2][3]. As long as your version of arrow-rs includes these updates (which post-date March 2026), this functionality will be available [1][4].Citations:
🏁 Script executed:
Repository: lance-format/lance
Length of output: 6921
🏁 Script executed:
Repository: lance-format/lance
Length of output: 4492
🏁 Script executed:
Repository: lance-format/lance
Length of output: 3694
🏁 Script executed:
Repository: lance-format/lance
Length of output: 6024
Use
arrow_array::record_batch!()hereThis test can build the
LargeBinaryandUInt64columns directly fromjsonbandrow_ids, removing the manualSchema/RecordBatch::try_newboilerplate.🤖 Prompt for AI Agents
Source: Coding guidelines