[
https://issues.apache.org/jira/browse/CASSANDRA-12367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487263#comment-15487263
]
Russell Bradberry commented on CASSANDRA-12367:
-----------------------------------------------
{quote}
I am not sure how it will work like tracing with SIZE ON? When you issue a
query after SIZE ON, will it give the size of the query or CQL partition?
{quote}
In this case it would be the size of the query, if you want the size of a given
partition then you would run a query specifying only the partition key.
{quote}
Also we will need the size before every read or write. This will cause calling
SIZE ON and then OFF after every operation.
{quote}
Why? I was suggesting this for the CQL specific representation, the internal
representation could still be a JMX call. If the client needs it for every
read/write then it would just always be on, just as if you wanted to have the
trace information for every read/write.
> 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)
