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

FLASH-796: support rename pk column #379

Merged
merged 14 commits into from
Jan 11, 2020
Merged

FLASH-796: support rename pk column #379

merged 14 commits into from
Jan 11, 2020

Conversation

hanfei1991
Copy link
Member

@hanfei1991 hanfei1991 commented Dec 30, 2019

When changing pk column, we should change the pk_ast in MergeTreeData at the same time。
test is added in full_stack_test, because common integration tests don't support create pk col.

@hanfei1991 hanfei1991 changed the title [WIP] try to print some log support rename pk column Jan 7, 2020
@@ -247,44 +259,37 @@ void SchemaBuilder<Getter>::applyDiff(const SchemaDiff & diff)
switch (diff.type)
{
case SchemaActionCreateTable:
case SchemaActionRecoverTable:
{
case SchemaActionRecoverTable: {
Copy link
Member Author

Choose a reason for hiding this comment

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

changed by clang-format

@hanfei1991
Copy link
Member Author

/run-integration-tests

@hanfei1991
Copy link
Member Author

/run-integration-tests

1 similar comment
@hanfei1991
Copy link
Member Author

/run-integration-tests

@hanfei1991
Copy link
Member Author

/run-integration-tests

1 similar comment
@hanfei1991
Copy link
Member Author

/run-integration-tests

@hanfei1991 hanfei1991 requested a review from zanmato1984 January 8, 2020 13:45
@zanmato1984 zanmato1984 changed the title support rename pk column FLASH-796: support rename pk column Jan 9, 2020
if (params.size() != 1)
{
throw Exception("There is an internal error for rename columns", ErrorCodes::LOGICAL_ERROR);
throw Exception("There is an internal error for rename columns, params size should be 1", ErrorCodes::LOGICAL_ERROR);
Copy link
Contributor

Choose a reason for hiding this comment

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

When you are reporting errors like this, it's always better to say "SOME SIZE is Y, should be X" than "SOME SIZE is not X".

Copy link
Contributor

@zanmato1984 zanmato1984 left a comment

Choose a reason for hiding this comment

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

LGTM

@hanfei1991
Copy link
Member Author

/run-integration-tests

@hanfei1991
Copy link
Member Author

/run-integration-tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants