[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923085#comment-16923085
]
Andy Tolbert commented on CASSANDRA-14825:
------------------------------------------
+1. I tried this out again and left some review comments on the [pull
request|https://github.com/apache/cassandra/pull/284]. The only non-trivial
suggestion I have is to make the topic a clustering column (i.e. {{table_name}}
in {{system_views.describe_table}} should be a clustering column) so you can
make a query such as 'show me all tables in this keyspace'. On the other hand
I can see 'give me the entire schema for this keyspace' and 'give me the schema
for this particular thing' as more valuable usecases, this would be more of a
'nice to have'.
> Expose table schema for drivers
> -------------------------------
>
> Key: CASSANDRA-14825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/CQL
> Reporter: Chris Lohfink
> Assignee: Chris Lohfink
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 1h 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
