[
https://issues.apache.org/jira/browse/CASSANDRA-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588210#comment-14588210
]
Benedict commented on CASSANDRA-9499:
-------------------------------------
bq. Are we going to shoot for a different encoding?
I think so, but it's still up for discussion.
bq. There is no guarantee I can get extra space in the buffer for the writer to
perform a putLong. Some implementations will not resize the buffer.
Ah. CommitLog. Yes, that is annoying, and pretty much nothing can be done about
it, other than padding the space we allocate for the CL record (which wouldn't
actually be dreadful). OK, nevermind. Forget both optimisations (the read is a
little ugly, and if we mostly expect small values, it's of dubious benefit). We
can revisit at a later date.
> 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)
