[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923747#comment-16923747
]
Benedict edited comment on CASSANDRA-14825 at 9/5/19 9:34 PM:
--------------------------------------------------------------
Perhaps we should break this deadlock with a non-binding vote? Possibly on the
mailing list? Since there's no obvious consensus, except that we should pick
one of the two, it looks set to go round in circles if we don't just pick one
and go with it.
was (Author: benedict):
Perhaps we should break this deadlock with a non-binding vote? Possibly on the
mailing list? Since nobody feels strongly, it looks set to go round in circles
if we don't just pick an approach and go with 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: 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]
