[ https://issues.apache.org/jira/browse/CASSANDRA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431092#comment-17431092 ]
Jacek Lewandowski commented on CASSANDRA-17044: ----------------------------------------------- btw. I was really surprised that there are new Cassandra specific {{Future}} and {{Duration}} implementations. There can be some inconsistency around those classes in the PR for trunk because my primary PR is against 4.0 and I used {{CompletableFuture}} and {{Duration}} from Java. I don't have any opinion on the new {{Future}} implementation yet apart from that it should be renamed so that it is easily distinguishable from the native Java's {{Future}} and Netty's {{Future}}. For {{Duration}} I would really remove it as it does not seem to bring any value and is not compatible with native {{java.time}} classes. > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org