[
https://issues.apache.org/jira/browse/CASSANDRA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067274#comment-13067274
]
Hudson commented on CASSANDRA-2916:
-----------------------------------
Integrated in Cassandra #960 (See
[https://builds.apache.org/job/Cassandra/960/])
ensure that we never estimate 0 keys when streaming non-empty ranges
patch by Stu Hood; reviewed by jbellis for CASSANDRA-2916
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148029
Files :
*
/cassandra/trunk/test/unit/org/apache/cassandra/streaming/StreamingTransferTest.java
* /cassandra/trunk/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
*
/cassandra/trunk/src/java/org/apache/cassandra/streaming/IncomingStreamReader.java
> Streaming estimatedKey calculation should never be 0
> ----------------------------------------------------
>
> Key: CASSANDRA-2916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments:
> 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
>
>
> The new in-streaming SSTable rebuild uses the sender's estimated key
> calculation to determine which codepath to take: in some cases, samples can
> result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
