Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1826302632.60761262754234523.JavaMail.jira@brutus.apache.org>
Date: Wed, 6 Jan 2010 05:03:54 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-669) Handle mmapping index files
 greater than 2GB
In-Reply-To: <1331728184.45751262707135771.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-669:
------------------------------------------

fix the -- in the xml in 02, and change BUFFER_SIZE to long in 03 as well to force the promotion of the position parameter.

> 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-use-long-for-mmap-segment-position-instead-of-int-whic.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.