History¶

2.0.1 (2019-12-20)¶

The method google.cloud.bigquery.job.QueryJob.result() is used again to wait for a google job to be completed. The timeout bug described in the previous “bugfixes” seems to be due to a Docker configuration problem.
The end of a step “query_to_bq” produced the log: “Ended source to bq”. It has been corrected to “Ended query to bq”.

The parameters delete_in_bq, delete_in_gs and delete_in_local of the load methods do not exist anymore. There were used to choose if data had to be deleted once loaded to the next location. The new behavior is now the following:
- The data is kept in the source.
- The data is deleted in transitional locations after being transferred.
This behavior is safer, simpler to understand and fits to the common use.
The destination parameter of google_pandas_load.loader.Loader.load() can no longer be set to ‘query’ since it appeared to be useless. It is now restricted to ‘bq’, ‘gs’, ‘local’ or ‘dataframe’.
The gs_dir_path_in_bucket parameter of google_pandas_load.loader.Loader has been renamed gs_dir_path.
google_pandas_load.loader.Loader has now the following getter functions: bq_client, dataset_ref, bucket, gs_dir_path and local_dir_path. They return the homonym arguments of the class.
google_pandas_load.loader_quick_setup.LoaderQuickSetup has three new getter functions: project_id, dataset_id and bucket_name. They return the homonym arguments of the class.

The method google.cloud.bigquery.job.QueryJob.result() was used to wait for a google job to be completed. It appeared it could lead to a timeout if the google job was too long to run and is threfore no longer used. Instead, the google job is reloaded every second until it is completed.