| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Update batch/transaction to push themselves onto client's stack, rather than batches. Updated API-invoking methods to take 'client', rather than 'connection', falling back to the client held by self. See #944.
Also remove symbols imported for conveniences from '_implicit_environ'.
Sorry, something went wrong.
|
I'm not as fussy as you about the commit history -- if you'd like, I can just squash the whole PR into a single commit. |
Sorry, something went wrong.
|
I'm not that fussy. I think re-committing the "Update batch/transaction/query to hold client." commit only to remove those changes later is a bit silly, but not worth arguing over. (Just re-read my comment yesterday, noticed "moral" instead of "normal", unintentionally a bit dramatic by me! Reviews from phone will do that to you.) Your "git style" can lead to issues like that since you always add review changes as new commits. In this case (this PR and #978) you're better off using git cherry-pick on the upstream commits than git rebase. Code LGTM. Feel free to merge. |
Sorry, something went wrong.
Co-authored-by: Lingqing Gan <lingqing.gan@gmail.com>
Co-authored-by: Lingqing Gan <lingqing.gan@gmail.com>
* fix(deps): require google-cloud-audit-log >= 0.3.1 * update constraints-3.8.txt * remove dev
* fix(deps): require google-cloud-audit-log >= 0.3.1 * update constraints-3.8.txt * remove dev
… RESOURCE_EXHAUSTD (#979) * fix: Make retry policy back off more aggressively for RPCs that retry RESOURCE_EXHAUSTD PiperOrigin-RevId: 557935020 Source-Link: googleapis/googleapis@38e1f31 Source-Link: googleapis/googleapis-gen@5bbe39d Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNWJiZTM5ZDM3MjE4YTQyMGIyMzY4YzM3NTQxZGU1ODg3ZGI3ZDZhZiJ9 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
chore: relocate owl bot post processor
This change allows the user to run a [dry run query](https://docs.cloud.google.com/bigquery/docs/samples/bigquery-query-dry-run?hl=en) using the `read_gbq` function. Instead of returning a `pd.DataFrame`, the behavior is changed and the amount of data processed (in GB) is returned. --------- Co-authored-by: Shenyang Cai <sycai@users.noreply.github.com> Co-authored-by: Shuowei Li <shuowei@google.com> Co-authored-by: Shenyang Cai <sycai@google.com>
PR created by the Librarian CLI to initialize a release. Merging this PR will auto trigger a release. Librarian Version: v0.7.0 Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:c8612d3fffb3f6a32353b2d1abd16b61e87811866f7ec9d65b59b02eb452a620 <details><summary>pandas-gbq: 0.33.0</summary> ## [0.33.0](googleapis/python-bigquery-pandas@v0.32.0...v0.33.0) (2026-01-05) ### Features * add dry run to the read_gbq function (#979) ([516f986f](googleapis/python-bigquery-pandas@516f986f)) </details> --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Source-Link: googleapis/synthtool@eaef28e Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:f8ca7655fa8a449cadcabcbce4054f593dcbae7aeeab34aa3fcc8b5cf7a93c9e Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: Anthonios Partheniou <partheniou@google.com>
| Back | FazBrowse Home | New Git URL |
Uses #978 as a base.
Final cleanup for #944.