[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923720#comment-16923720
]
Andy Tolbert commented on CASSANDRA-14825:
------------------------------------------
{quote}
I think you misunderstood Robert Stupp's comment above. He's not saying we
should stick to cqlsh-based DESCRIBE, he's mentioning the alternative to the
virtual table approach of having DESCRIBE being a genuine CQL (server-side)
command, one that would return result sets (and that I describe in a number of
comments above).
{quote}
I understand what he's referencing in context of the discussion of providing
server-side {{DESCRIBE}}, that is, not cqlsh {{DESCRIBE}}) support. The
virtual table approach is something that there is an available patch for that
works perfectly fine and will meet a lot of use cases, whereas server-side
{{DESCRIBE}} does not yet exist and may require more discussion. Given that
and that the virtual table implementation is rather concise(300 lines), I felt
it pragmatic to consider doing both.
> 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 50m
> 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]
