[
https://issues.apache.org/jira/browse/CASSANDRA-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564988#comment-14564988
]
Benedict commented on CASSANDRA-9499:
-------------------------------------
bq. because we have better control over which integer we actually encode
This is essentially my goal, along with much better performance for the
encoding/decoding In particular CASSANDRA-9498 seems to have been caused by a
lack of access to these methods, so having them available in our standard
toolkit to make conscious decisions about will likely lead to better, cleaner
code, with less risk of these (admittedly rare to encounter) bugs, with a side
order of improved performance.
As discussed briefly on IRC, if there is a lack of time before 3.0 we can
settle for the EncodedD(I/O)S, and just using write/readInt in CASSANDRA-9498.
I completely agree we should eliminate EncodedD(I/O)S once we deliver this.
TL;DR: Yep :)
> 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)
