[ 
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448699#comment-16448699
 ] 

Dinesh Joshi edited comment on CASSANDRA-7622 at 4/23/18 9:29 PM:
------------------------------------------------------------------

[~blerer] do you have a design or code that you can share? It would be great if 
you can post it. Is there a timeline around when you'll post it?
{quote}As there is already some effort going on for a proper pluggable storage 
solution, I came to the conclusion that we should drop that idea of {{Virtual 
Table}} and simply expose the system information through what we could call 
{{System Views}}. It will make the transition easier for people coming from the 
relational word and will help us to focus on what is really important for users 
which is the usability of the all thing.
{quote}
I am not fussy about naming. However, using the same terminology does confuse 
users as they may expect the same feature set from Cassandra as they got in 
their relational database. I would personally avoid it.


was (Author: djoshi3):
[~blerer] do you have a design or code that you can share? It would be great if 
you can post it. Is there a timeline around when you'll post it?

> 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

Reply via email to