Github user ifesdjeen commented on a diff in the pull request: https://github.com/apache/cassandra/pull/269#discussion_r219410710 --- Diff: src/java/org/apache/cassandra/dht/RangeStreamer.java --- @@ -446,16 +447,14 @@ else if (useStrictConsistency) //The old behavior where we might be asked to fetch ranges we don't need shouldn't occur anymore. //So it's an error if we don't find what we need. if (oldEndpoints.isEmpty() && toFetch.isTransient()) - { throw new AssertionError("If there are no endpoints to fetch from then we must be transitioning from transient to full for range " + toFetch); - } - if (!any(oldEndpoints, isSufficient)) + if (toFetch.isFull() && (oldEndpoints.isEmpty() || oldEndpoints.get(0).isTransient())) --- End diff -- My main problem with `!any` is that it negates. Iteration is harder to reason about when negated in my opinion. But this is fairly minor so I'm fine with leaving it as it was
--- --------------------------------------------------------------------- To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org For additional commands, e-mail: pr-h...@cassandra.apache.org