You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Etienne Chauchot (Jira)" <ji...@apache.org> on 2019/12/12 16:14:00 UTC
[jira] [Resolved] (BEAM-8894) Fix multiple coder bug in new spark
runner
[ https://issues.apache.org/jira/browse/BEAM-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne Chauchot resolved BEAM-8894.
------------------------------------
Fix Version/s: Not applicable
Resolution: Not A Problem
Lack of definition of the model in that case. Should runners re-encode ? Waiting for a common definition among runners, all runners exclude this test.
> Fix multiple coder bug in new spark runner
> ------------------------------------------
>
> Key: BEAM-8894
> URL: https://issues.apache.org/jira/browse/BEAM-8894
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Labels: structured-streaming
> Fix For: Not applicable
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test below does not pass. I fails with an EOF while calling NullableCoder(BigEndianCoder.decode)
> 'org.apache.beam.sdk.transforms.FlattenTest.testFlattenMultipleCoders'
> In the "old" spark runner, this test passes because it never call the NullableCoder because there is no serialization done.
> There may be a problem in the NullableCoder itself
--
This message was sent by Atlassian Jira
(v8.3.4#803005)