[jira] [Commented] (CASSSIDECAR-493) CachingSchemaStore should be reloaded when Schemastore kafka configs are changed

["Saranya Krishnakumar (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSSIDECAR-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106681#comment-18106681 ] 

Saranya Krishnakumar commented on CASSSIDECAR-493:
--------------------------------------------------

+1

> CachingSchemaStore should be reloaded when Schemastore kafka configs are changed
> --------------------------------------------------------------------------------
>
>                 Key: CASSSIDECAR-493
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-493
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Improvement
>          Components: CDC
>            Reporter: Jyothsna Konisa
>            Priority: Major
>             Fix For: 0.5
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Schemastore configuration is stored alongside the rest of CDC's Kafka config, there's no separate config source for it. So when that table is updated, anything derived from it should be rebuilt, including the schema publisher. CachingSchemaStore.loadPublisher() builds the TableSchemaPublisher from CdcConfigImpl.kafkaConfigs() and caches it as an instance field, a one-time snapshot, never re-read on demand. If the schema config is missing/invalid when this runs, it throws, gets caught and logged, and publisher stays null/stale.
> The only retry trigger today is ON_SIDECAR_SCHEMA_INITIALIZED. ON_CDC_CONFIGURATION_CHANGED should also be added as a trigger.



--
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