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

ASF subversion and git services commented on AIRFLOW-6091:
----------------------------------------------------------

Commit ee7d311867897feec490fcd2f9e1eb040c9db078 in airflow's branch 
refs/heads/v1-10-test from zuku1985
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=ee7d311 ]

[AIRFLOW-6091] Add flushing in execute method for BigQueryCursor (#6683)

If you execute multiple queries results of old ones will be
flushed allowing to read results of recent execute without
any issues.

(cherry picked from commit 0cf9598b0885cb94eb89c5eca8717f2245cb5de7)


> BigQueryCursor doesn't properly clean buffer, page_token and all_pages_loaded 
> before starting .execute() method
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-6091
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6091
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: hooks
>    Affects Versions: 1.10.6
>            Reporter: Tomasz Żukowski
>            Assignee: Tomasz Żukowski
>            Priority: Major
>
> There are two cases when it might be dangerous:
>  * If you run cursor.execute() and cursor.fetchall() and then once again 
> cursor.execute() for another query cursor.fetchall() will return empty list 
> because will be still set to True
>  * If you run cursor.execute() and cursor.fetchone() or fetchmany() and don't 
> read whole results and then run cursor.execute() with different query next 
> call to next will return data from old job which will be still stored in 
> buffer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to