[jira] [Commented] (CASSANDRA-7622) Implement virtual tables

["Tupshin Harper (JIRA)" <ji...@apache.org>]

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

Tupshin Harper commented on CASSANDRA-7622:
-------------------------------------------

The correct decision to make JMX bind to localhost only for security reasons creates additional importance and urgency for this as a feature.

I'd like to promote it from hand-wavey 3.x to more concrete 3.1 in hopes that it wouldn't slip from there. We really need to simplify the access patterns and reduce the surface area.

> Implement virtual tables
> ------------------------
>
>                 Key: CASSANDRA-7622
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tupshin Harper
>            Assignee: Benjamin Lerer
>             Fix For: 3.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
(v6.3.4#6332)