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

Posted to commits@cassandra.apache.org by "Jeff Jirsa (Jira)" <ji...@apache.org> on 2024/04/02 20:00:03 UTC

[jira] [Commented] (CASSANDRA-17044) Refactor schema management to allow for schema source pluggability

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

Jeff Jirsa commented on CASSANDRA-17044:
----------------------------------------

[~jjordan]  - you mentioned "A CEP around this is in process, should be ready to propose in the next week" - did you folks ever publish that? 

 
 

> Refactor schema management to allow for schema source pluggability
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-17044
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17044
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Schema
>            Reporter: Jacek Lewandowski
>            Assignee: Jacek Lewandowski
>            Priority: Normal
>             Fix For: 4.1-alpha1, 4.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The idea is decompose `Schema` into separate entities responsible for different things. In particular extract what is related to schema storage and synchronization into a separate class so that it is possible to create an extension point there and store schema in a different way than `system_schema` keyspace, for example in etcd. 
> This would also simplify the logic and reduce the number of special cases, make all the things more testable and the logic of internal classes encapsulated.



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