[
https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299242#comment-14299242
]
Matt Byrd commented on CASSANDRA-7688:
--------------------------------------
So I suppose the reason for suggesting exposing the same call via cql,
was that at least abstractly it was clear what this meant.
I concede that plumbing all this through might not be straightforward.
The problem with putting it in a system table is, what exactly do you put there?
The current computation is a somewhat expensive on demand computation that is
generally done relatively rarely.
Was your intent to just periodically execute this function and dump the results
into system tables?
Or did you have something different in mind?
> Add data sizing to a system table
> ---------------------------------
>
> Key: CASSANDRA-7688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7688
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jeremiah Jordan
> Assignee: Aleksey Yeschenko
> Fix For: 2.1.3
>
>
> Currently you can't implement something similar to describe_splits_ex purely
> from the a native protocol driver.
> https://datastax-oss.atlassian.net/browse/JAVA-312 is open to expose easily
> getting ownership information to a client in the java-driver. But you still
> need the data sizing part to get splits of a given size. We should add the
> sizing information to a system table so that native clients can get to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
