[ 
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924320#comment-16924320
 ] 

Aleksey Yeschenko commented on CASSANDRA-14825:
-----------------------------------------------

I think I've been on all three sides of this argument over the past years.

Ever since I rewrote the schema system tables for 3.0 in CASSANDRA-6717, the 
code to generate 3.0+ from system tables has been relatively easy. It will 
become even easier in 4.0 with {{COMPACT STORAGE}} gone. So I've never felt 
strongly about a need to have a server-side {{DESCRIBE}} variant in any shape 
or form.

But, much like [~slebresne], I've come around since then. There is value in a 
server-side {{DESCRIBE}} implementation. Less than there was before, and will 
be even less once 4.0 is out, but there still is.

Now, I love that we have virtual tables now, and I can see this functionality 
implemented using them. But my preference would be slightly in favour of moving 
{{cqlsh}} {{DESCRIBE}} into its set of standalone CQL statements, on balance. 
It's not at all invasive, IMO, but would allow us to have nice tailored 
grammar, more flexible than a generic {{SELECT}} statement could ever be.

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to