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
Adding support for ALTER RENAME COLUMN query to Distributed table engine #10727
Adding support for ALTER RENAME COLUMN query to Distributed table engine #10727
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.
Ok. And could you please also add a simple functional test (that will use test_shard_localhost or something similar)?
This is recommended because this functional test will fail more quickly and in more obvious way (than integration test) if RENAME COLUMN suddenly disappear.
Ok, I will add a stateless test as well. |
@alesapin, is this exception normal?
|
Also, there is a couple of these exceptions.
|
Adding renaming of the time column used inside the TTL expression after insert.
Updated test |
But it still does not. |
@alexey-milovidov, I am looking into the failing tests. Any ideas why there are so many fails related to zookeeper (https://clickhouse-test-reports.s3.yandex.net/10727/089371ddfb596a7b052ac709a5c2778e76f349c0/integration_tests_(release)/integration_run.7.txt.out.log)? |
Actually test |
@vzakaznikov It means that one of ZooKeeper nodes refusing our connections, but I don't know why it is happening. |
These fails also look very interesting https://clickhouse-test-reports.s3.yandex.net/10727/089371ddfb596a7b052ac709a5c2778e76f349c0/integration_tests_(asan)/integration_run.7.txt.out.log |
Out of all the fails I can only see that |
@alesapin, please see a new test https://github.com/ClickHouse/ClickHouse/blob/9780da3e747726086cf705281775af98f38a3e0c/tests/queries/0_stateless/01277_alter_rename_column_constraint_expr.sql which shows that CONSTRAINT expressions are not being updated when one of the columns used inside the expression is renamed. |
@@ -0,0 +1,17 @@ | |||
DROP TABLE IF EXISTS visits; |
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 think these tests are not related to changes. Let's make separate PR.
finally: | ||
drop_distributed_table(node1, table_name) | ||
|
||
def test_rename_distributed_parallel_insert_and_select(started_cluster): |
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 think we need to simplify this test. Which scenario do we check here?
@@ -0,0 +1,43 @@ | |||
DROP TABLE IF EXISTS table_for_rename; |
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 have stolen this test in my PR #10847 :)
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Adding support for ALTER RENAME COLUMN query to Distributed table engine.
Detailed description / Documentation draft:
Adding support for ALTER RENAME COLUMN query to Distributed table engine.