10BC0 docs: add info about streaming quota limits to `insert_rows*` methods by aribray · Pull Request #1409 · googleapis/python-bigquery · GitHub
[go: up one dir, main page]

Skip to content

Conversation

aribray
Copy link
Contributor
@aribray aribray commented Nov 15, 2022

Adds additional information about streaming quota limits to the following methods:

  • insert_rows()
  • insert_rows_json()
  • insert_rows_from_dataframe()
BigQuery will reject insertAll payloads that exceed a defined limit (10MB). 
Additionally, if a payload vastly exceeds this limit, the request is rejected
by the intermediate architecture, which returns a 413 (Payload Too Large) status code.

Fixes #1296 🦕

@product-auto-label product-auto-label bot added size: s Pull request size is small. api: bigquery Issues related to the googleapis/python-bigquery API. labels Nov 15, 2022
@aribray aribray marked this pull request as ready for review November 15, 2022 22:18
@aribray aribray requested a review from a team November 15, 2022 22:18
@aribray aribray requested a review from a team as a code owner November 15, 2022 22:18
@aribray aribray requested a review from mhlgio November 15, 2022 22:18
@shollyman shollyman removed the request for review from mhlgio November 18, 2022 16:58
@aribray aribray merged commit 0f08e9a into googleapis:main Nov 18, 2022
@aribray aribray deleted the aribray--insert-rows-docs branch November 18, 2022 18:43
abdelmegahedgoogle pushed a commit to abdelmegahedgoogle/python-bigquery that referenced this pull request Apr 17, 2023
…googleapis#1409)

* docs: add information about streaming quota limits (413: Payload Too Large)

Co-authored-by: Anthonios Partheniou <partheniou@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigquery Issues related to the googleapis/python-bigquery API. size: s Pull request size is small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Returned API errors are an HTML rendering, causing exception in client

3 participants

0