[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448330#comment-16448330
]
Benjamin Lerer edited comment on CASSANDRA-7622 at 4/23/18 3:45 PM:
--------------------------------------------------------------------
{quote}You do not get {{CREATE TABLE USING CompactionStats compaction_stats}},
it still displays the schema how you would expect with a {{create table....}}
output because thats the way cqlsh is created to take a schema and display
it.{quote}
Do not get me wrong. Both approach have some issues in my opinion even if
{{CREATE TABLE USING CompactionStats compaction_stats}} is less misleading. The
problem of displaying the table as a normal one is that it let the user believe
that it is a normal table which is not the case in many ways.
{quote} While I think its possible to use that shim to do other things I very
much doubt it would ever be used as such.{quote}
Then we do not need that logic. It is wrong in my opinion to add some logic
just in case we might need it one day.
was (Author: blerer):
{quote}You do not get {{CREATE TABLE USING CompactionStats compaction_stats}},
it still displays the schema how you would expect with a {{create table....}}
output because thats the way cqlsh is created to take a schema and display
it.{quote}
Do not get me wrong. Both approach have some issues in my opinion even if
{{{{CREATE TABLE USING CompactionStats compaction_stats}}}} is less misleading.
The problem of displaying the table as a normal one is that it let the user
believe that it is a normal table which is not the case in many ways.
{quote} While I think its possible to use that shim to do other things I very
much doubt it would ever be used as such.{quote}
Then we do not need that logic. It is wrong in my opinion to add some logic
just in case we might need it one day.
> 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: [email protected]
For additional commands, e-mail: [email protected]
