[
https://issues.apache.org/jira/browse/CASSANDRA-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587967#comment-14587967
]
Benedict commented on CASSANDRA-9499:
-------------------------------------
It's worth noting, of course, that the existing scheme has a very narrow useful
band around that unlikeliness threshold, after which it jumps up to 3 bytes,
instead of 2. So the poorly behaved users are penalised more strongly. I kind
of expect we'll have either everyone behaving well (so 1 byte in either
scheme), or people behaving quite badly, and jumping up to 3 bytes. But either
way, some boundary usecases win, some lose. It's always the way.
> Introduce writeVInt method to DataOutputStreamPlus
> --------------------------------------------------
>
> Key: CASSANDRA-9499
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9499
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Ariel Weisberg
> Priority: Minor
> Fix For: 3.0 beta 1
>
>
> CASSANDRA-8099 really could do with a writeVInt method, for both fixing
> CASSANDRA-9498 but also efficiently encoding timestamp/deletion deltas. It
> should be possible to make an especially efficient implementation against
> BufferedDataOutputStreamPlus.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
