cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9498) If more than 65K columns, sparse layout will break
Date Thu, 23 Jul 2015 19:02:05 GMT

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

Benedict commented on CASSANDRA-9498:
-------------------------------------

We need to switch {{writeShort}} to {{writeUnsignedVInt}} in a few places. This actually affects
more than sparse layout, with {{Columns.Serializer}} also needing updating.

We should probably reconsider all of our uses of {{writeShort}}, as it may be they would all
do better vint encoded.

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

Mime
View raw message