-
Notifications
You must be signed in to change notification settings - Fork 333
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
base: main
Are you sure you want to change the base?
feat: support alter add multiple columns #5262
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
CI says:
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) |
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? |
c2b2c49
to
c2a2b47
Compare
Makes sense. Let me try this after this PR got merged. |
Codecov ReportAttention: Patch coverage is
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 |
There are some conflicts |
c2a2b47
to
17beb2a
Compare
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.
Sorry for the late review. I have a few suggestions about the syntax.
#[derive(Debug, Clone, PartialEq, Eq, Visit, VisitMut, Serialize)] | ||
pub struct AddColumn { | ||
pub column_def: ColumnDef, | ||
pub location: Option<AddColumnLocation>, | ||
} |
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.
Can we implement Display
for this struct? All statement structs should support Display
.
src/sql/src/parsers/alter_parser.rs
Outdated
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 | ||
} |
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 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:
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.
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) |
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 call this method from parse_add_columns
I added in this PR, I removed self
.
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.