Fix behavior for reattach_state parameter in BigQueryInsertJobOperator #40664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to attach to RUNNING (but also any other state too) BQ Job using BigQueryInsertJobOperator, even though reattach_states={'PENDING', 'RUNNING'} parameter is set and Job is still running, ValueError: Job already begun is thrown.
Attaching to DONE job, which according to documentation shouldn't be possible (from airflow doc: if job with given id already exists then it tries to reattach to the job if its not done and its state is in reattach_states. If the job is done the operator will raise AirflowException.), but throws an error, as well as with any other Job type because of the validation in job._begin() call and fails if it's different than None.
This PR fixes this by adding checks of the current state before going to execute the Job in deferrable or synch mode.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.