[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454730#comment-16454730
]
Jon Haddad edited comment on CASSANDRA-7622 at 4/26/18 7:22 PM:
----------------------------------------------------------------
For what it's worth, I wrote an internal TLP tool that takes every JMX metric
and stores it in a sqlite DB, and I'm doing it virtually the same way [~cnlwsu]
has listed above. Yes, it requires grabbing the key you want up front, but as
[~cnlwsu] notes, in every practical use of these tables so does the alternative
proposed by [~blerer].
Assuming there's a trivial way to grab all the possible metrics that can be
used from a different view, it makes sense to me to expose the metrics in the
way [~cnlwsu] has, so I'm in favor of his approach as an operator.
was (Author: rustyrazorblade):
For what it's worth, I wrote an internal TLP tool that takes every JMX metric
and stores it in a sqlite DB, and I'm doing it the same with [~cnlwsu] has
listed above. Yes, it requires grabbing the key you want up front, but as
[~cnlwsu] notes, in every practical use of these tables so does the alternative
proposed by [~blerer].
Assuming there's a trivial way to grab all the possible metrics that can be
used from a different view, it makes sense to me to expose the metrics in the
way [~cnlwsu] has, so I'm in favor of his approach as an operator.
> 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
>
> Attachments: screenshot-1.png
>
>
> 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]
