[
https://issues.apache.org/jira/browse/BEAM-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132061#comment-17132061
]
Beam JIRA Bot commented on BEAM-1462:
-------------------------------------
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.
> DirectRunner unnecessarily re-scheules tasks after exceptions
> -------------------------------------------------------------
>
> Key: BEAM-1462
> URL: https://issues.apache.org/jira/browse/BEAM-1462
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P2
> Labels: newbie, stale-P2, starter
>
> Seems like DirectRunner keeps scheduling tasks when exceptions occur when
> reading BigQuery results (and possibly in other cases).
> I verified that rescheduling is not coming from BigQuery. AFAIKT a
> _MonitorTask that gets added at following location does not get removed
> properly when an exception is thrown.
> https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/direct/executor.py#L361
> To reproduce:
> (1) Raise a 'ValueError' at the beginning of method
> BigQueryWrapper.convert_row_to_dict at following location.
> https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/bigquery.py#L1061
> (2) Setup Python SDK and run bigquery_tornadoes with DirectRunner.
> python -m apache_beam.examples.cookbook.bigquery_tornadoes --output <table>
> --project <project>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
