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 2016/06/23 22:21:16 UTC
[jira] [Updated] (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:all-tabpanel ]
Luke Cwik updated BEAM-372:
---------------------------
Description:
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*.
was:
Add a test to CoderProperties that does the following:
1. Encode a value using the Coder
2. Add a byte at the end of the encoded array
3. Decode the value using the Coder
4. Verify the extra byte was not consumed
(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*.
> 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: Davor Bonaci
> 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)