[
https://issues.apache.org/jira/browse/CASSANDRA-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587818#comment-14587818
]
Sylvain Lebresne commented on CASSANDRA-9499:
---------------------------------------------
bq. It's a real shame we can't modify the encoding, or at least, it's not worth
the effort.
Do double-check cause I might be forgetting something but I believe we
currently only use vint encoding for the (serializing) row cache, which means
we still can change the encoding as it pleases us. And if doing so can make
things better, I think we should (it'll be much harder later when we use this
in sstables).
Maybe it could also make sense to have an "unsigned" variant for when we know
the value written is positive.
And as a nit, I think it would be convenient in practice to have methods for
{{int}} (at least as far as reading is concerned, though we'll want the writing
counterpart for symmetry) for when you deserialize something that's going into
a {{int}} anyway (for instance an array size).
> 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)
