[
https://issues.apache.org/jira/browse/CASSANDRA-19129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928948#comment-17928948
]
Bernardo Botella Corbi commented on CASSANDRA-19129:
----------------------------------------------------
I'd like to come back to this one. We have been discussing on adding a new
system table for driver support of constraints (check this
[Jira|https://issues.apache.org/jira/browse/CASSANDRA-20331]), and it seems
that we want to use virtual tables instead. I am going to raise a question on
the ML around how we want to approach this. I see two different approaches:
- Moving all the tables at once and making sure the driver can find them
- We take an incremental approach of moving one by one, splitting the work in
chunks
If we decide to go with the latter, I will create all the required Jiras for
the different tables.
> Virtualise system_schema
> ------------------------
>
> Key: CASSANDRA-19129
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19129
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Cluster/Schema
> Reporter: Marcus Eriksson
> Priority: Normal
> Fix For: 5.x
>
>
> Schema no longer needs to use `system.schema` for persistence as current
> schema is now part of {{ClusterMetadata}}. The existing tables have been
> preserved for client compatibility but we should review this moving forward
> and consider whether this could be switched to a virtual keyspace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
