[jira] [Commented] (BEAM-1462) DirectRunner unnecessarily re-scheules tasks after exceptions

["Kenneth Knowles (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546259#comment-17546259 ] 

Kenneth Knowles commented on BEAM-1462:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18141

> 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: P3
>              Labels: newbie, 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.20.7#820007)