You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/10/15 17:10:00 UTC
[jira] [Commented] (BEAM-10710) Fix the error message strings for
runtime type check errors
[ https://issues.apache.org/jira/browse/BEAM-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214841#comment-17214841 ]
Beam JIRA Bot commented on BEAM-10710:
--------------------------------------
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.
> Fix the error message strings for runtime type check errors
> -----------------------------------------------------------
>
> Key: BEAM-10710
> URL: https://issues.apache.org/jira/browse/BEAM-10710
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: Saavan Nanavati
> Priority: P2
> Labels: stale-P2
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, runtime type check errors yield [error messages|https://bit.ly/312zFs2] that display the label of a transform prefixed with 'ParDo'.
> * For instance, an error in a DoFn named 'ToInt' would show up as 'ParDo(ToInt)' in the error message.
> * However, this is incorrect behavior in certain cases, such as with Maps or Composite ParDo's. These should not be prefixed with 'ParDo'.
>
> This Jira issue would update the error messages to more accurately reflect the nature of the original transform. Tests would need to be updated to reflect the new error string changes as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)