[
https://issues.apache.org/jira/browse/CASSANDRA-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2280:
--------------------------------------
Attachment: 2280-v5.txt
bq. what about having the list of CFs only in StreamRequestMessage and add the
list of cfs to use as an argument to StreamOut.transferRanges()
Good idea. Done in v5. Also some refactoring so the different transferRanges
methods share the same code. (The one for SRVH wasn't actually ever calling
session.close which apparently we don't rely on yet, but it was a bug waiting
to happen.)
bq. In StreamRequestMessage, we should write the operation type even if version
is VERSION_080
Ah... Now I understand what you meant last time. Fixed.
bq. Nitpick: and couldn't we use the cf ids instead of the names ?
Done.
bq. In StreamRequestMessage, the field is a Collection but we're still using
Iterables.size() inside
Fixed.
bq. I suppose the bump of MessagingService from 2 to 81 was on purpose ? (I
don't mind, just pointing out to make sure)
My thought was that way we'll have VERSION_081=81 next, but I don't care a
great deal either.
> 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: 0.8.1
>
> 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
