You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matt Byrd (JIRA)" <ji...@apache.org> on 2014/08/08 23:21:12 UTC

[jira] [Commented] (CASSANDRA-7688) Add data sizing to a system table

    [ https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091315#comment-14091315 ] 

Matt Byrd commented on CASSANDRA-7688:
--------------------------------------

Originally I was just thinking of exposing the same method available in thrift, via some cql syntax i.e:
essentially from StorageProxy:
   public List<Pair<Range<Token>, Long>> getSplits(String keyspaceName, String cfName, Range<Token> range, int keysPerSplit, CFMetaData metadata)

This in turn actually operates on the index intervals in memory, getting appropriately sized splits given the samples taken.

Can you please elaborate on what the idea is behind storing this info in a system table?
It would seem that you would need to keep doing the above computation or something similar and write the result to a system table.
I would have thought it’d be easier to just expose the Storage proxy call via cql?

> 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
>             Fix For: 2.1.1
>
>
> 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.2#6252)