You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/05/28 08:35:17 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-9498) If more than 65K columns, sparse layout will break

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

Benedict updated CASSANDRA-9498:
--------------------------------
    Comment: was deleted

(was: [~aweisberg]: do you mind, and have the time to, take a look at this in conjunction with CASSANDRA-9500?)

> If more than 65K columns, sparse layout will break
> --------------------------------------------------
>
>                 Key: CASSANDRA-9498
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9498
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Priority: Minor
>             Fix For: 3.0 beta 1
>
>
> Follow up to CASSANDRA-8099. It is a relatively small bug, since the exposed population of users is likely to be very low, but fixing it in a good way is a bit tricky. I'm filing a separate JIRA, because I would like us to address this by introducing a writeVInt method to DataOutputStreamPlus, that we can also exploit to improve the encoding of timestamps and deletion times, and this JIRA will help to track the dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)