cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14825) Expose table schema for drivers
Date Fri, 09 Nov 2018 15:52:00 GMT


Andy Tolbert commented on CASSANDRA-14825:

[1]: but re-drivers, at least the existing ones, let's say I'm unconvinced this will simply
their life. 

Not in the near term, as long as drivers support versions older than a release with this change,
which will be a long time, the java and python driver will still need to generate CQL DDL
for those older versions.  The benefit to the drivers is more off in the future.  The primary
value add I see to this change is that it unbinds CQL DDL generation from specific driver
implementations, allowing any client capable of connecting to C* to extract schema CQL DDL.

> Expose table schema for drivers
> -------------------------------
>                 Key: CASSANDRA-14825
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message