You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2026/10/20 04:40:00 UTC

[jira] [Created] (CASSANALYTICS-207) Isolate per-table failures during CachingSchemaStore schema refresh

Yifan Cai created CASSANALYTICS-207:
---------------------------------------

             Summary: Isolate per-table failures during CachingSchemaStore schema refresh
                 Key: CASSANALYTICS-207
                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-207
             Project: Apache Cassandra Analytics
          Issue Type: Bug
          Components: CDC
            Reporter: Yifan Cai


CachingSchemaStore.onSchemaChange and publishSchemas convert every table in one loop with no per-table error handling. One table whose schema cannot be converted to Avro (for example a quoted column name that is not a valid Avro field name) aborts the refresh, skips stale-entry cleanup, and leaves the tables after it on stale or missing schemas; the failure is not logged from the future either. This change handles failures per table, logs and counts them, and always runs the cleanup.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org