[
https://issues.apache.org/jira/browse/CASSANDRA-12367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484582#comment-15484582
]
Russell Bradberry edited comment on CASSANDRA-12367 at 9/12/16 4:40 PM:
------------------------------------------------------------------------
I agree with [~thobbs] that it doesn't really belong in CQL directly. The
writeTime and ttl meta information in CQL is at the column level and makes
sense. What about exposing it in the same way that TRACING is exposed? where
setting something like "SIZES ON" will modify the output and can be implemented
in the clients in a similar fashion
This way, the size of the query can be returned and the user doesn't have to
modify the query to understand how it is stored.
was (Author: devdazed):
I agree with [~thobbs] that it doesn't really belong in CQL directly. The
writeTime and ttl meta information in CQL is at the column level and makes
sense. What about exposing it in the same way that TRACING is exposed? where
setting something like "SIZES ON" will modify the output and can be implemented
in the clients in a similar fashion
> 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)
