[
https://issues.apache.org/jira/browse/CASSANDRA-8747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict updated CASSANDRA-8747:
--------------------------------
Description:
Currently openEarly does some fairly ugly looping back over the summary data
we've collected looking for one we think should be fully covered in the Index
and Data files, and that should have a safe boundary between it and the end of
an IndexSummary entry so that when scanning across it we should not
accidentally read an incomplete key. The approach taken is a little difficult
to reason about though, and be confident of. Since we're cleaning up the
behaviour around this code, it seemed worthwhile to improve its clarity and
make its behaviour easier to reason about. The current behaviour can be
characterised as:
Find the first summary record
> Make SSTableWriter.openEarly behaviour more obvious
> ---------------------------------------------------
>
> Key: CASSANDRA-8747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8747
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1.4
>
>
> Currently openEarly does some fairly ugly looping back over the summary data
> we've collected looking for one we think should be fully covered in the Index
> and Data files, and that should have a safe boundary between it and the end
> of an IndexSummary entry so that when scanning across it we should not
> accidentally read an incomplete key. The approach taken is a little difficult
> to reason about though, and be confident of. Since we're cleaning up the
> behaviour around this code, it seemed worthwhile to improve its clarity and
> make its behaviour easier to reason about. The current behaviour can be
> characterised as:
> Find the first summary record
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
