cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1258) rebuild indexes after streaming
Date Thu, 29 Jul 2010 13:15:19 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893606#action_12893606
] 

Jonathan Ellis commented on CASSANDRA-1258:
-------------------------------------------

thanks

but now it occurs to me, since the root of the problem is SSTableReader, shouldn't we push
the comparator in there, instead of using if statements to avoid calling SSTR.getComparator?

sorry for the run-around...

> rebuild indexes after streaming
> -------------------------------
>
>                 Key: CASSANDRA-1258
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1258
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Nate McCall
>             Fix For: 0.7 beta 1
>
>         Attachments: 1258-v4.txt, 1258-v5.txt, 1258-v6.txt, 1258-v7.txt, trunk-1258-src-2.txt,
trunk-1258-src-3.txt
>
>
> since index CFSes are "private," they won't be streamed with other sstables.  which is
good, because the normal partitioner logic wouldn't stream the right parts anyway.
> seems like the right solution is to extend SSTW.maybeRecover to rebuild indexes as well.
 (this has the added benefit of being able to use streaming as a relatively straightforward
"bulk loader.")

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message