Open tellienne opened 1 month ago
we tried to exclude the column from replication and make it materialized on the clickhouse side:
column.exclude.list: "public.test.business_id"
and after that:
ALTER TABLE test.supplier_product_cards ON CLUSTER '{cluster}' modify COLUMN business_id String MATERIALIZED (((12::character varying(255)::text || lpad(number::character varying(255)::text, 6, 0::character varying(255)::text))))
but the connector is still trying to insert data into this column. seems to be related to this https://github.com/Altinity/clickhouse-sink-connector/issues/357
Hi! we use a connector to transfer data from postgres to clickhouse. version: altinityinfra/clickhouse-sink-connector: 716-f3f63a01328216e766609fa8280adbe93b7ea320-lt
noticed that after some time the connector loses some columns in the tables. logs entry:
looks like the column was removed from the table in postgres, however the table schema was not changed, the column exists. the column cannot be empty, but the connector thinks it doesn't exist and tries to insert null. Because of this, data transfer stops.
the columt business_id has ddl like
the problem has been reproduced several times for tables where there is such a generated column like business_id