[
https://issues.apache.org/jira/browse/CASSANDRA-12367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449351#comment-15449351
]
Sylvain Lebresne commented on CASSANDRA-12367:
----------------------------------------------
bq. We need this feature now so we can do it with CQL and then when virtual
tables are implemented, move this feature there. What do you think Sylvain
Lebresne
With all due respect, that's not really an argument. I'm staying on my position
that the proposed CQL mechanism is imo weird, unintuitive and ad-hoc (from a
CQL standpoint) and I really think we shouldn't do it that way. I get that
"you" want it, but we have to think of the good of the software in general, and
stuffs are much more easy to add than remove, so adding something "ugly" now to
change it later don't really work. I'd be ok with focusing on JMX only for this
ticket and creating a new one to do it well in CQL, which again probably means
using this has initial motivation for introducing the virtual table mechanism
we've been talking about, and I'm even happy helping with that as I think 1)
this would be more generally useful anyway and 2) I'm not sure it's *that* hard
in practice.
> Add an API to request the size of a CQL partition
> -------------------------------------------------
>
> Key: CASSANDRA-12367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12367
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Geoffrey Yu
> Assignee: Geoffrey Yu
> Priority: Minor
> Fix For: 3.x
>
> Attachments: 12367-trunk-v2.txt, 12367-trunk.txt
>
>
> It would be useful to have an API that we could use to get the total
> serialized size of a CQL partition, scoped by keyspace and table, on disk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
