You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/05/28 08:25:00 UTC
[jira] [Updated] (BEAM-12420) TypeDescriptor information gets lost
when applying multiple DoFn on Composite Transform
[ https://issues.apache.org/jira/browse/BEAM-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía updated BEAM-12420:
--------------------------------
Status: Open (was: Triage Needed)
> TypeDescriptor information gets lost when applying multiple DoFn on Composite Transform
> ---------------------------------------------------------------------------------------
>
> Key: BEAM-12420
> URL: https://issues.apache.org/jira/browse/BEAM-12420
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Ismaël Mejía
> Priority: P2
>
> While working on BEAM-12384 to preserve correctly the typeDescriptor of the Read transform. I noticed that ParDo passes the outputType information into the next transforms by taking the output of `getOutputTypeDescriptor` specified in the `DoFn`, but the subsequent transform does not get the full inputTypeDescriptor.
> There are other open questions:
> 1. How can we make this easier for users who rarely override the getOutputTypeDescriptor?
> 2. Where the typeDescriptor should come in the SDF case, from the Restriction?
> For more details:
> https://github.com/apache/beam/pull/14854#issuecomment-848793500
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)