-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Table structure out of sync. #64146
Comments
clickhouse-keeper:23.8.8.21.altinitystable |
What steps led to this problem? What command did you execute? |
create table CREATE TABLE IF NOT EXISTS `local_1`.`appname_6` ON CLUSTER dtstack (`_at_timestamp_` DateTime64(3, 'UTC'),`_at_date_` Date,`_receive_timestamp_` DateTime64(3, 'UTC'),`_tenant_id_` Int64,`__appname__` LowCardinality(String)) engine = ReplicatedMergeTree('/clickhouse/tables/1/appname_6/2024-05-20/{shard}/hits', '{replica}') partition by toString(_at_date_) order by (_at_date_, _at_timestamp_, intHash64(toInt64(toDateTime(_at_timestamp_))))
2024-05-20 21:23:13 ERR acos-loggie-multiarch/pkg/pipeline/pipeline.go:368 > consumer batch failed: load table:[local_1.appname_6] failed: table create error, tableName: appname_6: code: 122, message: There was an error on [chi-clickhouse-cluster-dtstack-0-0:9000]: Code: 122. DB::Exception: Table columns structure in ZooKeeper is different from local table structure. Local columns:
columns format version: 1
5 columns:
`_at_timestamp_` DateTime64(3, \'UTC\')
`_at_date_` Date
`_receive_timestamp_` DateTime64(3, \'UTC\')
`_tenant_id_` Int64
`__appname__` LowCardinality(String)
Zookeeper columns:
columns format version: 1
5 columns:
`__appname__` LowCardinality(String)
`_at_timestamp_` DateTime64(3, \'UTC\')
`_at_date_` Date
`_receive_timestamp_` DateTime64(3, \'UTC\')
`_tenant_id_` Int64
. (INCOMPATIBLE_COLUMNS) (version 24.3.2.23 (official build)) |
What steps led to this problem?
|
This is a mistake. We don't support alternative, third-party builds. Read https://clickhouse.com/docs/knowledgebase/difference_between_official_builds_and_3rd_party |
Why does this issue occur? Will adjusting database_atomic_delay_before_drop_table_sec help? Could you help explain?
The text was updated successfully, but these errors were encountered: