[
https://issues.apache.org/jira/browse/BEAM-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131993#comment-17131993
]
Beam JIRA Bot commented on BEAM-1956:
-------------------------------------
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.
> Flatten operation should respect input type hints.
> --------------------------------------------------
>
> Key: BEAM-1956
> URL: https://issues.apache.org/jira/browse/BEAM-1956
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Vikas Kedigehalli
> Priority: P2
> Labels: stale-P2
>
> Input type hints are currently not respected by the Flatten operation and
> instead `Any` type is chosen as a fallback. This could lead to using a pickle
> coder even if there was a custom coder type hint provided for input
> PCollections.
> Also, this could lead to undesirable results, particularly, when a Flatten
> operation is followed by a GroupByKey operation which requires the key coder
> to be deterministic. Even if the user provides deterministic coder type hints
> to their PCollections, defaulting to Any would result in using the pickle
> coder (non-deterministic). As a result of this, CoGroupByKey is broken in
> such scenarios where input PCollection coder is deterministic for the type
> while pickle coder is not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
