cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-7688) Add data sizing to a system table
Date Tue, 02 Jun 2015 11:29:18 GMT


Piotr Kołaczkowski commented on CASSANDRA-7688:

I double checked the cassandra.size_recorder_interval option does indeed work, but because
many tests are creating fresh keyspaces.tables, the interval of 1 second is still too large
and the test manages to run before the estimates are created. We'd need to put Thread.sleep
before all the tests, which we're not going to do, because it would  So far we just removed
the warning about missing estimates. But it would be nice if C* filled those estimate entries
on table creation (even with zeroes). There is a difference between "we don't know the estimates"
and "we know there are no data". 

> Add data sizing to a system table
> ---------------------------------
>                 Key: CASSANDRA-7688
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jeremiah Jordan
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.1.5
>         Attachments: 7688.txt
> Currently you can't implement something similar to describe_splits_ex purely from the
a native protocol driver. 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

View raw message