[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821297#comment-16821297
]
Jonathan Ellis commented on CASSANDRA-14825:
--------------------------------------------
IMO the right UX for interacting with "what tables and keyspaces are defined"
is a system view and SELECT. SELECT composes by design with everything else
(WHERE, even UDF) in a way that DESCRIBE does not.
(It's fine to then say "we're not going to give you the schema in that view,
you need to use DESCRIBE if you want that" but I don't think that's necessarily
either better or worse.)
I think it's more important to get the composability right at the CQL level,
than give an easy way to get a full schema dump. I think the latter scenario
is much more niche and I'm fine with requiring a for loop to get it.
> 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: 0.5h
> 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
