[
https://issues.apache.org/jira/browse/BEAM-14052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531862#comment-17531862
]
Beam JIRA Bot commented on BEAM-14052:
--------------------------------------
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.
> Input type annotation of MapTuple and FlatMapTuple are ignored
> --------------------------------------------------------------
>
> Key: BEAM-14052
> URL: https://issues.apache.org/jira/browse/BEAM-14052
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Yu Feng
> Priority: P2
> Labels: stale-P2
>
> This is a tracking bug for the remaining issue of type annotation support in
> MapTuple and FlatMapTuple described in PR #16351.
> Consider 2 cases:
> - MapTuple(fn(a: int, b: int, *args))
> - MapTuple(fn(a: int, b: int, args: Tuple[Any, ...]))
> We unpack (1, 2, 3, 4) to a=1, b=1, args=(3, 4) in first case, but fail in
> second case.
> My concern is that the beam representation of these 2 signatures are *likely*
> the same:
> input_types[0] = (int, int, Tuple[Any, ...])
> input_types[1] = {}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
