Benjamin Lerer commented on CASSANDRA-7622:

One thing, I have some trouble with is to allow people to create their own 
Virtual Table. Once those things are given you cannot remove them easily and we 
will have to live with them for a really long time. The API being quite 
flexible I can imagine a lot of way of abusing of it. All the use cases I have 
ever seen  mentioned are about providing access to some local server 
information. I would really be in favor of limiting the patch to that. 

It is easier to open that functionality later on that having to try to block it 
or remove it. 

> Implement virtual tables
> ------------------------
>                 Key: CASSANDRA-7622
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
>             Project: Cassandra
>          Issue Type: Improvement
>            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 
> A possible implementation would be in terms of CASSANDRA-7443, but I am not 
> presupposing.

This message was sent by Atlassian JIRA

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

Reply via email to