-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH: BQ Job Id in verbose output #70
Conversation
Codecov Report
@@ Coverage Diff @@
## master #70 +/- ##
===========================================
- Coverage 73.37% 28.21% -45.17%
===========================================
Files 4 4
Lines 1540 1542 +2
===========================================
- Hits 1130 435 -695
- Misses 410 1107 +697
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on this change. Job ID is the first thing the support people and BigQuery team ask for when something doesn't go right.
can you add a note in the whatsnew (for 0.2.0)? otherwise lgtm. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tworec !
This is ready to merge once a change log entry is added. Something like:
read_gbq
now displays the BigQuery Job ID when verbose output is enabled. (:issue:70
)
ok, here goes changelog entry |
docs/source/changelog.rst
Outdated
@@ -7,7 +7,8 @@ Changelog | |||
- Drop support for Python 3.4 (:issue:`40`) | |||
- The dataframe passed to ```.to_gbq(...., if_exists='append')``` needs to contain only a subset of the fields in the BigQuery schema. (:issue:`24`) | |||
- Use the `google-auth <https://google-auth.readthedocs.io/en/latest/>`__ library for authentication because oauth2client is deprecated. (:issue:`39`) | |||
- ``read_gbq`` now has a ``auth_local_webserver`` boolean argument for controlling whether to use web server or console flow when getting user credentials. Replaces `--noauth_local_webserver` command line argument (:issue:`35`) | |||
- ``read_gbq`` now has a ``auth_local_webserver`` boolean argument for controlling whether to use web server or console flow when getting user credentials. Replaces `--noauth_local_webserver` command line argument. (:issue:`35`) | |||
- read_gbq now displays the BigQuery Job ID in verbose output. (:issue:`70`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please can you add double back ticks around read_gbq? Otherwise, this looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Hi,
After few years of BQ usage I've reached point where I need to report support case to Google BQ Team.
I've attached my iPython notebook with pandas gbq output, but they needed query Job IDs.
This is simple change to add them in read_gbq.
I'm not using to_gbq at all so I've not added verbose output for it when I implemented read_gbq some time ago. Today it is still not much verbose so I leaving things as they are.