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

Change MySQL engine configuration when the mysql is not accessable #13398

Open
shwangdev opened this issue Aug 6, 2020 · 2 comments · Fixed by #28054
Open

Change MySQL engine configuration when the mysql is not accessable #13398

shwangdev opened this issue Aug 6, 2020 · 2 comments · Fixed by #28054
Labels
question Question?

Comments

@shwangdev
Copy link

I have a database in clickhouse which is using MySQL engine. However, for some reason the IP of that mysql server was changed. I can not drop the db in clickhouse , cause it reports can not access the old mysql ip.
So, how can I change the db engine configuration in clickhouse?

@shwangdev shwangdev added the question Question? label Aug 6, 2020
Avogar added a commit that referenced this issue Aug 26, 2021
tavplubix added a commit that referenced this issue Aug 27, 2021
tavplubix added a commit that referenced this issue Aug 28, 2021
@tavplubix
Copy link
Member

Reopen, because #28054 was reverted (so we don't forget to fix the test and merge it again)

@tavplubix tavplubix reopened this Sep 8, 2021
@baxitashraf
Copy link

Yes, you can change the Table engine.

CREATE TABLE example_table (id UInt32, data Float64)
ENGINE=MergeTree() ORDER BY id;

Insert into example_table values(1,1), (1,1), (2,1);

CREATE TABLE example_table1 (id UInt32, data Float64)
ENGINE=SummingMergeTree() ORDER BY id;

-- this does not copy any data (instant & almost free command)
alter table example_table1 attach partition tuple() from example_table;

optimize table example_table1 final;

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

Successfully merging a pull request may close this issue.

4 participants