You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/10/17 19:32:59 UTC
[jira] [Commented] (BEAM-469) NullableCoder optimized encoding via
passthrough context
[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583205#comment-15583205 ]
Daniel Halperin commented on BEAM-469:
--------------------------------------
Backwards compatibility: this is a change to the encoding of data, which will only affect Cloud Dataflow streaming pipelines across update. This is not yet part of the Beam model, and no one in Beam depends on it.
> NullableCoder optimized encoding via passthrough 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
> Assignee: Thomas Groh
> Priority: Trivial
> Labels: backward-incompatible
> Fix For: 0.3.0-incubating
>
>
> 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)