[
https://issues.apache.org/jira/browse/CASSANDRA-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105462#comment-13105462
]
Jonathan Ellis commented on CASSANDRA-2280:
-------------------------------------------
As mentioned above, we reverted it from 0.8.1 because of CASSANDRA-2818. We've
committed to maintaining drop-in-ability between minor releases, which means we
can't release protocol changes unless protocol backwards- and
forwards-compatibility actually works. In this case, 2818 was a
forwards-compatibility bug in 0.8.0 and 0.8.1 which means we'd have to say "to
upgrade to 0.8.x where x >= 6, you must first upgrade to 0.8.y where 2 <= y <
6." Which is super confusing to people and honestly, my experience is that 99%
of our users don't read NEWS before upgrading anyway so it's totally going to
bite a lot of them.
0.7 was not affected by 2818 but it's past the point where we should be making
protocol changes. Any change is risky and the bar is pretty high to make
changes to "oldstable," which is what 0.7 is now.
> Request specific column families using StreamIn
> -----------------------------------------------
>
> Key: CASSANDRA-2280
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2280
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Assignee: Jonathan Ellis
> Fix For: 1.0.0
>
> Attachments:
> 0001-Allow-specific-column-families-to-be-requested-for-str.txt,
> 0001-Allow-specific-column-families-to-be-requested-for-str.txt, 2280-v3.txt,
> 2280-v4.txt, 2280-v5.txt
>
>
> StreamIn.requestRanges only specifies a keyspace, meaning that requesting a
> range will request it for all column families: if you have a large number of
> CFs, this can cause quite a headache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
