You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/01/07 03:59:54 UTC

[jira] Resolved: (CASSANDRA-669) Handle mmapping index files greater than 2GB

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

Jonathan Ellis resolved CASSANDRA-669.
--------------------------------------

    Resolution: Fixed

committed

> 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.