You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Thomas Richter (Created) (JIRA)" <ji...@apache.org> on 2011/10/13 16:38:11 UTC
[jira] [Created] (CASSANDRA-3358) 2GB row size limit in ColumnIndex
offset calculation
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.8.7, 0.7.9, 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
[jira] [Updated] (CASSANDRA-3358) 2GB row size limit in ColumnIndex
offset calculation
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3358:
--------------------------------------
Affects Version/s: (was: 0.8.7)
(was: 0.7.9)
(was: 1.0.0)
0.7.0
Fix Version/s: 1.0.1
0.8.8
0.7.10
> 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.0
> Reporter: Thomas Richter
> Fix For: 0.7.10, 0.8.8, 1.0.1
>
>
> 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
[jira] [Resolved] (CASSANDRA-3358) 2GB row size limit in
ColumnIndex offset calculation
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3358.
---------------------------------------
Resolution: Fixed
Reviewer: jbellis
Assignee: Thomas Richter
committed the proposed fix, thanks!
> 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.0
> Reporter: Thomas Richter
> Assignee: Thomas Richter
> Fix For: 0.7.10, 0.8.8, 1.0.1
>
>
> 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
[jira] [Commented] (CASSANDRA-3358) 2GB row size limit in
ColumnIndex offset calculation
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126748#comment-13126748 ]
Hudson commented on CASSANDRA-3358:
-----------------------------------
Integrated in Cassandra-0.7 #554 (See [https://builds.apache.org/job/Cassandra-0.7/554/])
fix ColumnIndexer to use long offsets
patch by Thomas Richter; reviewed by jbellis for CASSANDRA-3358
jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1183000
Files :
* /cassandra/branches/cassandra-0.7/CHANGES.txt
* /cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/ColumnIndexer.java
> 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.0
> Reporter: Thomas Richter
> Assignee: Thomas Richter
> Fix For: 0.7.10, 0.8.8, 1.0.1
>
>
> 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
[jira] [Commented] (CASSANDRA-3358) 2GB row size limit in
ColumnIndex offset calculation
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ 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