[jira] [Commented] (BEAM-12420) TypeDescriptor information gets lost when applying multiple DoFn on Composite Transform

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-12420:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>              Labels: stale-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)