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

feat: support alter add multiple columns #5262

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

NiwakaDev
Copy link
Collaborator

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

This PR addresses #5243.

What's changed and what's your intention?

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.
  • This PR requires documentation updates.
  • API changes are backward compatible.
  • Schema or data changes are backward compatible.

@NiwakaDev NiwakaDev requested a review from a team as a code owner January 1, 2025 09:43
Copy link
Contributor

coderabbitai bot commented Jan 1, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the docs-not-required This change does not impact docs. label Jan 1, 2025
@NiwakaDev
Copy link
Collaborator Author

NiwakaDev commented Jan 1, 2025

CI says:

error: `havn` should be `haven`
  --> ./src/flow/src/adapter/table_source.rs:65:22
   |
65 |     /// If the table havn't been created in database, the tableId returned would be null
   |                      ^^^^

I don't add this line. Do I need to fix this?

@discord9
Copy link
Contributor

discord9 commented Jan 2, 2025

CI says:

error: `havn` should be `haven`
  --> ./src/flow/src/adapter/table_source.rs:65:22
   |
65 |     /// If the table havn't been created in database, the tableId returned would be null
   |                      ^^^^

I don't add this line. Do I need to fix this?

Nevermind, just a typo, feel free to fix it(or wait for #5265 to fix the typos)

@discord9
Copy link
Contributor

discord9 commented Jan 2, 2025

Would it be possible to consider adding support for dropping multiple columns as well, perhaps for the sake of symmetry? Given that the underlying proto definition already supports both adding and dropping multiple columns, the required changes should be fairly minimal. Do you think this would be a worthwhile addition, or is it unnecessary at this stage?

@NiwakaDev NiwakaDev force-pushed the feat/support_alter_add_columns branch from c2b2c49 to c2a2b47 Compare January 2, 2025 13:40
@NiwakaDev
Copy link
Collaborator Author

NiwakaDev commented Jan 2, 2025

@discord9

Would it be possible to consider adding support for dropping multiple columns as well, perhaps for the sake of symmetry? Given that the underlying proto definition already supports both adding and dropping multiple columns, the required changes should be fairly minimal. Do you think this would be a worthwhile addition, or is it unnecessary at this stage?

Makes sense. Let me try this after this PR got merged.

Copy link

codecov bot commented Jan 2, 2025

Codecov Report

Attention: Patch coverage is 95.34884% with 6 lines in your changes missing coverage. Please review.

Project coverage is 83.93%. Comparing base (353c823) to head (8956d10).
Report is 18 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5262      +/-   ##
==========================================
- Coverage   84.09%   83.93%   -0.16%     
==========================================
  Files        1199     1200       +1     
  Lines      224581   225432     +851     
==========================================
+ Hits       188866   189225     +359     
- Misses      35715    36207     +492     

@WenyXu
Copy link
Member

WenyXu commented Jan 3, 2025

There are some conflicts

@NiwakaDev NiwakaDev force-pushed the feat/support_alter_add_columns branch from c2a2b47 to 17beb2a Compare January 3, 2025 15:05
Copy link
Contributor

@evenyag evenyag left a comment

Choose a reason for hiding this comment

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

Sorry for the late review. I have a few suggestions about the syntax.

Comment on lines +88 to +92
#[derive(Debug, Clone, PartialEq, Eq, Visit, VisitMut, Serialize)]
pub struct AddColumn {
pub column_def: ColumnDef,
pub location: Option<AddColumnLocation>,
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we implement Display for this struct? All statement structs should support Display.

Comment on lines 190 to 207
let mut add_columns: Vec<AddColumn> = vec![];
loop {
let mut column_def = self.parser.parse_column_def().context(error::SyntaxSnafu)?;
column_def.name = Self::canonicalize_identifier(column_def.name);
let location = if self.parser.parse_keyword(Keyword::FIRST) {
Some(AddColumnLocation::First)
} else if let Token::Word(word) = self.parser.peek_token().token {
if word.value.eq_ignore_ascii_case("AFTER") {
let _ = self.parser.next_token();
let name = Self::canonicalize_identifier(
self.parse_identifier().context(error::SyntaxSnafu)?,
);
Some(AddColumnLocation::After {
column_name: name.value,
})
} else {
None
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer to require users to specify ADD before each column.

ALTER TABLE table_name
ADD COLUMN column_name1 data_type constraint,
ADD COLUMN column_name2 data_type constraint,
...
ADD COLUMN column_namen data_type constraint;

We may reuse the parse_comma_separated() to parse each ADD COLUMN operation.
https://github.com/apache/datafusion-sqlparser-rs/blob/main/src/parser/mod.rs#L7843

Refer to:

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Addressed your review.

pub(crate) fn parse_identifier(&mut self) -> std::result::Result<Ident, ParserError> {
self.parser.parse_identifier(false)
pub(crate) fn parse_identifier(parser: &mut Parser) -> std::result::Result<Ident, ParserError> {
parser.parse_identifier(false)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

To call this method from parse_add_columns I added in this PR, I removed self.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required This change does not impact docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants