Hey - weird one, ref upgrades - if we're upgrading manually - can you confirm how schema evolution should work for clickhouse?
Currently our process is to find your new tagged release, like 0.54.0 - identify any containers that have changed - i.e. collector, query service, migration service, ui service etc. Run a script to cache those containers locally in ECR.
We then run the migration container, then redeploy the other containers using that image. It's all worked perfectly, until today.
2024-09-12T17:00:59.545Z info exporterhelper/retry_sender.go:118 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "logs", "name": "clickhouselogsexporter", "error": "StatementSend:code: 10, message: Not found column attributes_bool.keys in block. There are only columns: ts_bucket_start, resource_fingerprint, timestamp, observed_timestamp, id, trace_id, span_id, trace_flags, severity_text, severity_number, body, attributes_string, attributes_number, attributes_bool, resources_string, scope_name, scope_version, scope_string: while pushing to view signoz_logs.attribute_keys_bool_final_mv (211bdbc2-196d-43ad-9f49-a31b13627556)", "interval": "3.047923669s"}
I presumed the migration service handled all that for us
