-
Notifications
You must be signed in to change notification settings - Fork 875
[#9015] improvement(lance-rest): Add UTs and ITs for Lance rest table operations #9016
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
Merged
yuqi1129
merged 14 commits into
apache:branch-lance-namepspace-dev
from
yuqi1129:issue_9015
Nov 5, 2025
Merged
Changes from 9 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c8ed9ad
Add UTs and ITs for Lance rest table operations
yuqi1129 099c546
Resolve comments
yuqi1129 39d0843
Resolve comments
yuqi1129 db9cf5b
Fix flaky test
yuqi1129 c21fbc6
Merge branch 'branch-lance-namepspace-dev' into issue_9015
yuqi1129 40a4fba
polish
yuqi1129 9509d11
Merge remote-tracking branch 'me/issue_9015' into issue_9015
yuqi1129 0d3524f
polish
yuqi1129 1e6d544
Some minor optimize
yuqi1129 3d1f379
Resolve comments.
yuqi1129 2867a47
fix again
yuqi1129 63491f0
refactor the file GravitinoLanceNamespaceWrapper
yuqi1129 0da982c
rename some files.
yuqi1129 0ed1dbd
Add final flag.
yuqi1129 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
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
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.
The
falsemeans "failed to store" or "the table not existed"? If the latter, it should returnfalse, not throwing an exception.The semantics are misleading; you need to confirm with @mchades .
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.
Generic lakehouse will return false if
the table not existed.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.
To be honest, the current code organization scatters the logic for table operations between
GenericLakehouseCatalogOperationandLanceCatalogOperation, which reduces code readability (you need to pay attention to both code logics when operating Lance tables) and introduces some repetitive operations (such as repeatedly gettingTable from store), I think we should consider this issue in our future refactoring.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.
BTW, why do you call
store.gettwice?The code here is confused; both the caller and callee will access the DB, and the callee handles some exceptions, but some rely on the caller.
The lance should only focus on lance-specific logic, whereas the generic lakehouse operation should only focus on the metadata-related CRUD operations.
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.
I agree, the implementation is not good, it messes with different logic, and doesn't clearly separate the responsibilities.