[ https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309060#comment-14309060 ]
Aleksey Yeschenko commented on CASSANDRA-7688: ---------------------------------------------- You are quoting the wrong code here, but how do you *not* background it? It's not strictly about cost, it's about not having any other triggering mechanism. When we add vtable support (cql tables backed by classes, not sstables) - then we'll switch sizing (and several other system sstables) to that. Until then, what other options do we have? This is a simple temporary replacement for describe_splits_ex, its *only* goal is to free Spark and others from having to maintain an extra Thrift connection *now*. Hence the lack of metrics or configurability of the refresh interval. I'm open to increasing/decreasing the hard-coded one, however, if you have better options. > 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 > > Attachments: 7688.txt > > > 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)