[
https://issues.apache.org/jira/browse/CASSANDRA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433720#comment-17433720
]
Alex Petrov commented on CASSANDRA-17044:
-----------------------------------------
I'd say, for the APIs where we expect significant changes, I'd say we should
not (and can not, really) make any guarantees whatsoever. For some of the APIs
(for which seems to be some discussion on ML), we should have at least some
stability. That said, say, if we have a 2i API, since our main goal as Apache
project is to maintain 2i implementations in-tree (be it SASI or, potentially,
SAI), if someone were to come and make a change, but at the same time adjust
the in-tree SASI and SAI implementations accordingly, I'd say we should allow
such a change. Maintainers of external indexes will have to adjust. What I
haven't considered when writing my previous comment is if we'll allow external
code to dictate what's good for the project, we may not be able to deliver the
changes in the best possible way.
> 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
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
