[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146709#comment-17146709
]
Dinesh Joshi commented on CASSANDRA-14825:
------------------------------------------
Hi [~blerer], the changes look ok but there are some failures that I think we
should investigate. I have kicked off a circleci jobs
([j11|https://circleci.com/workflow-run/7eb01c14-efa7-4f67-9172-c7e31bc42e33]
and
[j8|https://circleci.com/workflow-run/a2780b93-14f5-4e8e-8eae-2841ac412c07]) on
trunk to see if those failures are also on trunk. If they are then we're not
introducing a new regression so we can go ahead and merge.
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
