[
https://issues.apache.org/jira/browse/SAMZA-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226523#comment-14226523
]
Chris Riccomini commented on SAMZA-481:
---------------------------------------
Initially, I simply cloned the new IntegerSerde, but I wasn't crazy about the
serialization style:
{noformat}
The long data type is a 64-bit signed two's complement integer. It has a
minimum value of -9,223,372,036,854,775,808 and a maximum value of
9,223,372,036,854,775,807 (inclusive).
{noformat}
This was leading to bytes on the wire of -1, -1, -1, -127, .. etc. Not sure if
this is what we want or if we want a different style of encoding. I don't have
a strong preference. I took a look at Kryo, and it's also just using
ByteBuffer.putLong encoding. See also
[DataOutput.writeLong|https://docs.oracle.com/javase/7/docs/api/java/io/DataOutput.html#writeLong(long)].
> Write a LongSerde
> -----------------
>
> Key: SAMZA-481
> URL: https://issues.apache.org/jira/browse/SAMZA-481
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Labels: newbie
> Fix For: 0.9.0
>
>
> We ship with an IntegerSerde, but it'd be nice to support longs as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
