feat(catalog): Implement update_table for Hive metastore catalog#1894
feat(catalog): Implement update_table for Hive metastore catalog#1894vladson wants to merge 3 commits into
Conversation
vladson
force-pushed
the
hms_update_table
branch
from
3ffd73b to
b5c3d53
Compare
vladson
force-pushed
the
hms_update_table
branch
from
b5c3d53 to
bc562b7
Compare
|
Hi team, I would appreciate it if anyone could take a look at the PR, it's my first in iceberg-rust, but I hope it is in the spirit of the project. |
liurenjie1024
left a comment
liurenjie1024
left a comment
There was a problem hiding this comment.
Thanks @vladson for this pr, just finished first round of review.
| metainfo = { workspace = true } | ||
| motore-macros = { workspace = true } | ||
| volo = { workspace = true } | ||
| whoami = "1.6.1" |
There was a problem hiding this comment.
We manage dependencies in workspace's root cargo.tom.
There was a problem hiding this comment.
Hey, thank you @liurenjie1024 moved whoami to the main Cargo.
| let db_name = validate_namespace(ident.namespace())?; | ||
| let tbl_name = ident.name.clone(); | ||
|
|
||
| if self.config.props.contains_key(HMS_HIVE_LOCKS_DISABLED) { |
There was a problem hiding this comment.
I'm not a hive expert, but I would suggest to start with pessimistic version only first.
There was a problem hiding this comment.
Hey, I had some experience with Hive metastore, both in setting up and using it. The thing is that many are using optimistic locking, and the problem is that in a system with multiple clients, all must use no hive locks flow, as otherwise there is a risk of data loss.
My implementation of the environment context is in line with Trino and others.
Partial implementation of HMS traditional commit stabilising fix issues with hms lock flow refactoring for optimistic locks address format
vladson
force-pushed
the
hms_update_table
branch
from
e30fa08 to
f4072a0
Compare
|
Thank you for the review; I appreciate your effort! |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
|
Hi, is there any updates for this pull request ? |
|
Hi, I'll update it on weekend to be green. I believe we need it... |
|
reopened as #2684 |
3 participants
Which issue does this PR close?
What changes are included in this PR?
update_table for HMS catalog.
The implementation is based on other iceberg implementations, Trino and Hive code bases.
Are these changes tested?
The existing tests were modified, and extensive manual tests were performed.