cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8750) Ensure SSTableReader.last corresponds exactly with the file end
Date Wed, 11 Feb 2015 11:56:12 GMT

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

Benedict commented on CASSANDRA-8750:
-------------------------------------

This depends on CASSANDRA-8747. Any chance we could get a review on that (whomever) so we
can merge all of these related patches in and put them to rest?

> Ensure SSTableReader.last corresponds exactly with the file end
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-8750
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8750
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 2.1.4
>
>
> Following on from CASSANDRA-8744, CASSANDRA-8749 and CASSANDRA-8747, this patch attempts
to make the whole opening early of compaction results more robust and with more clearly understood
behaviour. The improvements of CASSANDRA-8747 permit is to easily align the last key with
a summary boundary, and an index and data file end position. This patch modifies SegmentedFile
to permit the provision of an explicit length, which is then provided to any readers, which
enforce it, ensuring no code may accidentally see an end inconsistent with the one advertised.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message