[
https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422385#comment-15422385
]
Mariusz Wojakowski commented on BEAM-469:
-----------------------------------------
Trying to understand: but we need to write down length? Unless we want to
encode/decode only one element using NullableCoder.
Please explain the usage of that to me - I'll try to do this task if you don't
mind.
> NullableCoder should encode using the context given and not always use the
> nested context
> -----------------------------------------------------------------------------------------
>
> Key: BEAM-469
> URL: https://issues.apache.org/jira/browse/BEAM-469
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Luke Cwik
> Priority: Trivial
>
> NullableCoder should encode using the context given and not always use the
> nested context. For coders which can efficiently encode in the outer context
> such as StringUtf8Coder or ByteArrayCoder, we are forcing them to prefix
> themselves with their length.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
