[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452213#comment-16452213
]
Benjamin Lerer commented on CASSANDRA-7622:
-------------------------------------------
{quote}You have 1 cell per attribute of each metric? theres currently 63
metrics with between 1 and 15 values - literally hundreds of cells per row
which isnt viewable on a sane display.
{quote}
This is a display problem not a schema problem. If you take the case of CQLSH
you can simply use {{EXPAND ON}} to print the output vertically.
{quote}I do have to say though, this ticket has been 4 years of bikeshedding,
kinda unfortunate timing to wait until theres an implementation in review to do
it from scratch instead of giving feedback.
{quote}
All my apologies.
I can understand your frustration. Now, the story is a bit different from what
you seem believe. In 2015, I decided to work on that ticket and assigned it to
me. Due to some priority changes, I did not manage to work on it and got
unassigned. Around mid-February, I wanted to come back to that ticket. At that
time it was assigned to Jeff and I knew he was not actively working on it. I
decided to create a patch on the DSE side. One month later the patch was in
review on our side and at the same time you updated this ticket.
I had some offline discussion with [~iamaleksey] this morning and he also has
some concerns about my patch. I will try to port the refactoring part of the
patch and the API used to plug {{SystemViews}} for next week. Once, it is done
it will be easier for everybody to judge what is good or bad about it.
Hopefully, we can end up with a solution that satisfy everybody.
> Implement virtual tables
> ------------------------
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Tupshin Harper
> Assignee: Chris Lohfink
> Priority: Major
> Fix For: 4.x
>
>
> There are a variety of reasons to want virtual tables, which would be any
> table that would be backed by an API, rather than data explicitly managed and
> stored as sstables.
> One possible use case would be to expose JMX data through CQL as a
> resurrection of CASSANDRA-3527.
> Another is a more general framework to implement the ability to expose yaml
> configuration information. So it would be an alternate approach to
> CASSANDRA-7370.
> A possible implementation would be in terms of CASSANDRA-7443, but I am not
> presupposing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
