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

Benedict commented on CASSANDRA-14825:
--------------------------------------

FWIW, I'm +1 the principle of this change.  The prior discussion didn't seem to 
touch on issues of modifications to the CQL syntax, such as renaming poorly 
named properties or otherwise updating the CQL language.  When you multiply 
this dimension with the dimension of clients having to parse multiple schema 
versions, it seems unlikely all clients will get this right.

That said, Aleksey's proposal of a virtual table holding a data dictionary for 
mapping things might work out.  But I'm unclear on exactly how it would work, 
it sound like a lot of work to accomplish, and I don't personally see a problem 
with providing this functionality anyway.

I also think there's independent value in a 'canonical' CQL string for a given 
database object.

> 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

Reply via email to