Skip to content

docs: add warning for bigframes 2.0 #1557

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

Merged
merged 11 commits into from
Mar 28, 2025
Merged

docs: add warning for bigframes 2.0 #1557

merged 11 commits into from
Mar 28, 2025

Conversation

Genesis929
Copy link
Collaborator

@Genesis929 Genesis929 commented Mar 27, 2025

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Staging result: https://screenshot.googleplex.com/4iMfjL9VsB7ZXy5

@Genesis929 Genesis929 requested review from tswast and shobsi March 27, 2025 22:21
@product-auto-label product-auto-label bot added size: s Pull request size is small. api: bigquery Issues related to the googleapis/python-bigquery-dataframes API. labels Mar 27, 2025
@Genesis929 Genesis929 marked this pull request as ready for review March 27, 2025 22:26
@Genesis929 Genesis929 requested review from a team as code owners March 27, 2025 22:26
README.rst Outdated
<p>Version 2.0 introduces breaking changes for improved security and performance. Key default behaviors have changed:</p>
<ul>
<li><strong>Large Results (&gt;10GB):</strong> The default value for <code>allow_large_results</code> has changed to False. Methods like <code>to_pandas()</code> will now fail if the query result's compressed data size exceeds 10GB, unless large results are explicitly permitted.</li>
<li><strong>Remote Function Security:</strong> The library no longer defaults to using the Compute Engine service account, and network ingress now defaults to "internal-only".</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] suggest rephrasing:

The library no longer automatically lets the Compute Engine default service account become the identity of the Cloud Run functions. If that is desired, it has to be indicated by passing cloud_function_service_account="default".

In addition, we should also call out:

Arguments to remote_function would have to be passed as keyword arguments.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, also added a new line for keyword arguments.

README.rst Outdated
<li><strong>Remote Function Security:</strong> The library no longer defaults to using the Compute Engine service account, and network ingress now defaults to "internal-only".</li>
<li><strong>Endpoint Connections:</strong> Automatic fallback to locational endpoints in certain regions is removed. </li>
</ul>
<p><strong>Important:</strong> If you are not ready to adapt to these changes, please pin your dependency to a version less than 2.0 (e.g., <code>bigframes==1.38.0</code>) to avoid disruption.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should say 1.42.0, as that is the latest release

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

@Genesis929 Genesis929 requested a review from shobsi March 28, 2025 01:16
@Genesis929 Genesis929 requested a review from shuoweil March 28, 2025 02:39
@tswast tswast enabled auto-merge (squash) March 28, 2025 16:43
@tswast tswast merged commit 3f0eaa1 into main Mar 28, 2025
18 of 24 checks passed
@tswast tswast deleted the warning_b2_huanc branch March 28, 2025 17:21
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-dataframes API. size: s Pull request size is small.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants