[ 
https://issues.apache.org/jira/browse/CASSANDRA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stu Hood updated CASSANDRA-2629:
--------------------------------

    Attachment: 0002-CASSANDRA-2629-Remove-the-retry-with-key-from-index-st.txt
                0001-CASSANDRA-2629-Move-key-and-row-size-reading-into-the-.txt

Patch to move key/length reading into the iterators. Applies atop the linked 
issues.

For convenience I removed a step from scrub in 0002 where if the key/length at 
the head of a row were corrupt, we retried with the key/length from the index. 
I'll understand if we want to add this back (would have to push it into the 
iterator), but either way we end up skipping the row as corrupt (using the 
index), so I don't think it is much of a loss.

> Move key reads into SSTableIterators
> ------------------------------------
>
>                 Key: CASSANDRA-2629
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2629
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 1.0
>
>         Attachments: 
> 0001-CASSANDRA-2629-Move-key-and-row-size-reading-into-the-.txt, 
> 0002-CASSANDRA-2629-Remove-the-retry-with-key-from-index-st.txt
>
>
> All SSTableIterators have a constructor that assumes the key and length has 
> already been parsed. Moving this logic inside the iterator will improve 
> symmetry and allow the file format to change without iterator consumers 
> knowing it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to