-
Notifications
You must be signed in to change notification settings - Fork 188
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
feat: sql catalog support update table #862
base: main
Are you sure you want to change the base?
Conversation
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.
Thanks @Li0k for this pr, but I have concerning introducing update table at this moment as there are many missing features such as conflict detection, commit retry.
|
||
/// Returns snapshot references. | ||
#[inline] | ||
pub fn snapshot_refs(&self) -> &HashMap<String, SnapshotReference> { |
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.
Why we add this method? We already have lookup method for snapshot
@@ -255,7 +255,7 @@ pub struct TableCreation { | |||
|
|||
/// TableCommit represents the commit of a table in the catalog. | |||
#[derive(Debug, TypedBuilder)] | |||
#[builder(build_method(vis = "pub(crate)"))] | |||
#[builder(build_method(vis = "pub"))] |
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 reason we make TableCommit
crate only is that we don't want to allow user to build it manually, all table commits construction should go through transaction api.
This PR support
update_table
interface for sql catalogupdate_table
Other PRs for reference:
After these PRs have been merged, we can use sql database as the catalog backend