You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2017/04/11 03:34:41 UTC

[jira] [Commented] (BEAM-463) BoundedHeapCoder should be a StandardCoder and not a CustomCoder

    [ https://issues.apache.org/jira/browse/BEAM-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963790#comment-15963790 ] 

Luke Cwik commented on BEAM-463:
--------------------------------

The motivation was about getting introspection into the coder components, even if a wrapping coder is only understood by some SDKs, the component coder could be understood by a runner and/or reused in other places. I can see the argument to treat this is an opaque coder that doesn't encode to anything which makes sense outside of the context of a specific SDK.

Also brings up a question as to whether all component coders always be listed even for CustomCoder like things?

> BoundedHeapCoder should be a StandardCoder and not a CustomCoder
> ----------------------------------------------------------------
>
>                 Key: BEAM-463
>                 URL: https://issues.apache.org/jira/browse/BEAM-463
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Luke Cwik
>            Priority: Minor
>              Labels: backward-incompatible
>             Fix For: First stable release
>
>
> The issue is that BoundedHeapCoder does not report component encodings which prevents effective runner inspection of the components.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)