[
https://issues.apache.org/jira/browse/BEAM-12855?focusedWorklogId=648848&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-648848
]
ASF GitHub Bot logged work on BEAM-12855:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/21 20:10
Start Date: 09/Sep/21 20:10
Worklog Time Spent: 10m
Work Description: robertwb commented on pull request #15476:
URL: https://github.com/apache/beam/pull/15476#issuecomment-916401900
I'm a little wary of this change. Currently, there's ambiguity as to what we
should do if a transform and its surrounding composite both declare a
(non-trivial) type constraint on an output PCollection. Previously, the inner
transform would win, but this changes it to let the outer transform win.
That might fix this test, but might break others.
One option is to actually address the TODO here and implement (best-effort?)
intersection.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@beam.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 648848)
Time Spent: 2h (was: 1h 50m)
> Infer result type when the composite type has Any
> -------------------------------------------------
>
> Key: BEAM-12855
> URL: https://issues.apache.org/jira/browse/BEAM-12855
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: P2
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Infer result type when the composite type has Any. This change makes
> `with_output_types` annotation work for composite transforms like
> `CombinePerKey`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
