[
https://issues.apache.org/jira/browse/BEAM-10169?focusedWorklogId=446931&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-446931
]
ASF GitHub Bot logged work on BEAM-10169:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jun/20 21:41
Start Date: 16/Jun/20 21:41
Worklog Time Spent: 10m
Work Description: lostluck merged pull request #11976:
URL: https://github.com/apache/beam/pull/11976
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 446931)
Time Spent: 7h 10m (was: 7h)
> ParDo* functions should declare the correct output N in their error message
> ---------------------------------------------------------------------------
>
> Key: BEAM-10169
> URL: https://issues.apache.org/jira/browse/BEAM-10169
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Aaron Tillekeratne
> Priority: P3
> Labels: noob, starter
> Time Spent: 7h 10m
> Remaining Estimate: 0h
>
> User report noted the confusion in the error if you use a DoFn with 0 outputs
> with beam.ParDo instead of beam.ParDo0.
> In that case, a panic stack trace is followed by the cryptic: "expected 1
> output. Found: []"
> We can do better.
> While we can't change the return signature dynamically (that's for ParDoN
> only), we can instead clearly indicate:
> * the DoFn in question.
> * the number of outputs the DoFn has
> * and recommend using ParDo0, ParDo, ParDo2,...ParDo7, or ParDoN, as
> appropriate.
> https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/pardo.go#L361
> would need to change as well as any of the specific cases that follow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
