You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jon Meredith (Jira)" <ji...@apache.org> on 2020/06/09 22:23:00 UTC

[jira] [Commented] (CASSANDRA-14825) Expose table schema for drivers

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

Jon Meredith commented on CASSANDRA-14825:
------------------------------------------

How's this going? Is anybody actively working on it as we near completion of all the alpha tickets?

> 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: Robert Stupp
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 4.0-alpha
>
>          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.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org