Skip to content
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

feature(planner): support table statements in new planner #5907

Merged
merged 11 commits into from
Jun 15, 2022

Conversation

andylokandy
Copy link
Collaborator

@andylokandy andylokandy commented Jun 11, 2022

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

  • DROP TABLE
  • ALTER TABLE
  • UNDROP TABLE
  • RENAME TABLE
  • TRUNCATE TABLE
  • OPTIMIZE TABLE
  • DESCRIBE TABLE

Changelog

  • New Feature

Related Issues

Closes #5774

@vercel
Copy link

vercel bot commented Jun 11, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated
databend ⬜️ Ignored (Inspect) Jun 15, 2022 at 10:38AM (UTC)

@mergify
Copy link
Contributor

mergify bot commented Jun 11, 2022

Thanks for the contribution!
I have applied any labels matching special text in your PR Changelog.

Please review the labels and make any necessary changes.

@mergify mergify bot added the pr-feature this PR introduces a new feature to the codebase label Jun 11, 2022
@andylokandy andylokandy marked this pull request as draft June 11, 2022 13:48
@andylokandy andylokandy changed the title feature(planner): suppport table statements in new planner feature(planner): support table statements in new planner Jun 11, 2022
@mergify
Copy link
Contributor

mergify bot commented Jun 15, 2022

This pull request has merge conflicts that must be resolved before it can be merged. @andylokandy please update it 🙏.

Try @mergify update or update manually.

@mergify mergify bot merged commit c0a46ee into databendlabs:main Jun 15, 2022
@@ -174,8 +174,8 @@ pub struct TableMeta {
pub engine: String,
pub engine_options: BTreeMap<String, String>,
pub options: BTreeMap<String, String>,
pub cluster_key: Option<String>,
// The vector of cluster keys.
pub current_cluster_key: Option<String>,
Copy link
Member

@zhyass zhyass Jun 15, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @andylokandy
I think default_cluster_key is better than current_cluster_key. Because we have a default_cluster_key_id already.
#6012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-review pr-feature this PR introduces a new feature to the codebase
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate TABLE related DDL statements to new planner
7 participants