[
https://issues.apache.org/jira/browse/CASSANDRA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797614#action_12797614
]
Hudson commented on CASSANDRA-669:
----------------------------------
Integrated in Cassandra #316 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/316/])
instead of providing a RandomAccessFile-like interface in FileDataInput
implementing seek and trying to keep people from shooting themselves in the
foot by forgetting that it may only represent a 2GB segment of a larger file,
provide an InputStream-like interface emphasizing mark/reset
patch by jbellis; tested by Brandon Williams for
add support for multiple mmapped index segments, and add mmap_index_only option
patch by jbellis; tested by Brandon Williams for
store data information for any index entries spanning a mmap segment boundary
when reading the index (with a BufferedRAF) so we don't have to deal with that
at read time.
patch by jbellis; tested by Brandon Williams for
> Handle mmapping index files greater than 2GB
> --------------------------------------------
>
> Key: CASSANDRA-669
> URL: https://issues.apache.org/jira/browse/CASSANDRA-669
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.9
>
> Attachments:
> 0001-store-data-information-for-any-index-entries-spanning-.txt,
> 0002-add-support-for-multiple-mmapped-index-segments-and-ad.txt,
> 0003-instead-of-providing-a-RandomAccessFile-like-interface.txt
>
>
> "Who would ever have an index file larger than 2GB?" I thought. Turns out
> it's not that hard with narrow rows... :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
