-
Notifications
You must be signed in to change notification settings - Fork 48
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
Alternate approach to get location for Bigquery tables #1449
Conversation
Codecov ReportBase: 97.32% // Head: 97.32% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1449 +/- ##
=======================================
Coverage 97.32% 97.32%
=======================================
Files 19 19
Lines 672 672
=======================================
Hits 654 654
Misses 18 18 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
58a75cb
to
95adc25
Compare
95adc25
to
77039fe
Compare
085bd70
to
bf9734f
Compare
bf9734f
to
4358476
Compare
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.
A better approach will cater to other operators in the future.
`numpy.int` was initially deprecated and now removed in 1.24 released yday ```python In [3]: numpy.int <ipython-input-3-1989d03c08d8>:1: DeprecationWarning: `np.int` is a deprecated alias for the builtin `int`. To silence this warning, use `int` by itself. Doing this will not modify any behavior and is safe. When replacing `np.int`, you may wish to use e.g. `np.int64` or `np.int32` to specify the precision. If you wish to review your current use, check the release note link for additional information. Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations numpy.int Out[3]: int ``` This (cherry picked from commit 745ab5f)
Addressed comments & Cloud IDE team is waiting for this release
An alternate approach to #1416
Also closes #1460
ToDo:
The
region
parameter passed to Table wasn't used anywhere except internally -- so going to remove it without deprecation