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/07/08 23:35:11 UTC
[jira] [Commented] (BEAM-372) CoderProperties: Test that the coder
doesn't consume more bytes than it produces
[ https://issues.apache.org/jira/browse/BEAM-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368718#comment-15368718 ]
Daniel Halperin commented on BEAM-372:
--------------------------------------
[~csingh] have you had any progress or blockers? Should I unassign?
> CoderProperties: Test that the coder doesn't consume more bytes than it produces
> --------------------------------------------------------------------------------
>
> Key: BEAM-372
> URL: https://issues.apache.org/jira/browse/BEAM-372
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Ben Chambers
> Assignee: Chandni Singh
> Priority: Minor
> Labels: beginner, newbie, starter
>
> Add a test to CoderProperties that does the following:
> 1. Encode a value using the Coder in the nested context
> 2. Decode the value using the Coder in the nested context
> 3. Verify that the input stream wasn't requested to consume any extra bytes
> (This could possibly just be an enhancement to the existing round-trip encode/decode test)
> When this fails it can lead to very difficult to debug situations in a coder wrapped around the problematic coder. This would be an easy test that would clearly fail *for the coder which was problematic*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)