[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662631#comment-16662631
]
Andy Tolbert commented on CASSANDRA-14825:
------------------------------------------
I think it is worth revisiting the discussion from [CASSANDRA-8005].
We should emphasize that the goal of this is not to benefit the drivers or that
the drivers would use this as part of it's schema parsing (we benefit from
[CASSANDRA-6717] and the previous 2.x schema tables for that).
Exposing the Schema DDL as a string is something some users and tools need, and
I think the server can do a better job representing this correctly and managing
changes release to release as the server only needs to concern itself with its
current view of the schema vs. the driver having to consider all versions.
I think two key points of discussion were:
1. Should an API exist that exposes the Schema creation statements as CQL (DDL)?
2. If yes, where should that exist?
Having the drivers generate and maintain this functionality with schema changes
happening release to release has not been easy. There is a lot of complexity
and it is a big ask for it to be done correctly by multiple driver
implementations. It is important that the schema CQL is correct, particularly
in the case where this functionality is being used by tools for backup/restore
or standing up new environments.
> Expose table schema for drivers
> -------------------------------
>
> Key: CASSANDRA-14825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Chris Lohfink
> Assignee: Chris Lohfink
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the drivers recreate the CQL for the tables by putting together the
> system table values. This is very difficult to keep up to date and buggy
> enough that its only even supported in Java and Python drivers. Cassandra
> already has some limited output available for snapshots that we could provide
> in a virtual table or new query that the drivers can fetch. This can greatly
> reduce the complexity of drivers while also reducing bugs like
> CASSANDRA-14822 as the underlying schema and properties change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
