Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 13 Oct 2011 15:48:11 +0000 (UTC)
From: "Jonathan Ellis (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1502590283.9646.1318520891849.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <195364036.9284.1318516691833.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3358) 2GB row size limit in
 ColumnIndex offset calculation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-3358:
-------------------------------------------

Weird -- you're absolutely right, but I could have sworn we fixed this already. :)
                
> 2GB row size limit in ColumnIndex offset calculation
> ----------------------------------------------------
>
>                 Key: CASSANDRA-3358
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3358
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.9, 0.8.7, 1.0.0
>            Reporter: Thomas Richter
>
> Index offset is calculated using int instead of long resulting in overflow at 2GB row size. As a result affected columns can not be retrieved. 
> Fix: use long instead of int

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira