You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Petrov (Jira)" <ji...@apache.org> on 2021/10/20 11:23:00 UTC
[jira] [Comment Edited] (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=17431150#comment-17431150 ]
Alex Petrov edited comment on CASSANDRA-17044 at 10/20/21, 11:22 AM:
---------------------------------------------------------------------
bq. I was really surprised that there are new Cassandra specific Future and Duration implementations.
If you check the context, the change was made in the context of [CEP-10|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-10%3A+Cluster+and+Code+Simulations], and right now your branch throws {{Illegal import - java.util.concurrent.CompletableFuture. [IllegalImport]}}. In short, you'll have to use the Cassandra-specific implementation. I'd ask [~paulo] and [~stefan.miklosovic] about Duration.
was (Author: ifesdjeen):
> I was really surprised that there are new Cassandra specific Future and Duration implementations.
If you check the context, the change was made in the context of [CEP-10|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-10%3A+Cluster+and+Code+Simulations], and right now your branch throws {{Illegal import - java.util.concurrent.CompletableFuture. [IllegalImport]}}. In short, you'll have to use the Cassandra-specific implementation. I'd ask [~paulo] and [~stefan.miklosovic] about Duration.
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org