[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924060#comment-16924060
]
Sylvain Lebresne commented on CASSANDRA-14825:
----------------------------------------------
I was trying to have an argumented and as-objective-as-possible discussion on
the pros and cons of each approach. I honestly don't feel there has been much
of that: a lot of the early conversation has dismissed the {{DESCRIBE}}
approach on clear mis-comprehension of the proposal (even the voting email
still talk of protocol changes, which is simply not part of the suggestion at
all), touting advantages of the virtual table approach that just aren't there;
the more recent arguments for why the virtual table approach would be superior
seems to be a tad subjective ("IMO the right UX", "more natural").
And in particular, no-one even acknowledged the points about "how do we
properly expose the internal parts of the schema". This ticket only feels stuck
because you guys have made up your mind and don't want to discuss it anymore,
not because all relevant points have been fully considered.
But with that said, I've done my job of raising the arguments I saw, and If
there is no interest in it, feel free to decide with a vote.
{quote}Given that and that the virtual table implementation is rather
concise(300 lines), I felt it pragmatic to consider doing both.
{quote}
My point against having 2 solutions for the same thing wasn't a line-of-code
consideration (at least not primarily, having 2 times 300 lines of code is
still worth than having only it one time for maintenance). It's a user-centric
concern. Having multiple ways to do the same thing is exactly the type of
things that further C* reputation of being hard to approach.
> 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]
