Skip to content

Adding HappyBase batch delete().#1537

Merged
dhermes merged 1 commit intogoogleapis:masterfrom
dhermes:happybase-finish-batch
Feb 25, 2016
Merged

Adding HappyBase batch delete().#1537
dhermes merged 1 commit intogoogleapis:masterfrom
dhermes:happybase-finish-batch

Conversation

@dhermes
Copy link
Copy Markdown
Contributor

@dhermes dhermes commented Feb 25, 2016

This completes the Batch() implementation.


All that is left is finishing Table! w00t! (And bringing over the HappyBase system tests.)

@dhermes dhermes added the api: bigtable Issues related to the Bigtable API. label Feb 25, 2016
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Feb 25, 2016
['cf1', None],
['cf2', None],
['cf3', ''],
['cf3', ''], # AGGGHHHHHHHHHH THIS IS WEIRD

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This completes the Batch() implementation.
@dhermes dhermes force-pushed the happybase-finish-batch branch from 3c147c2 to 00bfeda Compare February 25, 2016 23:25
dhermes added a commit that referenced this pull request Feb 25, 2016
@dhermes dhermes merged commit c05e7bd into googleapis:master Feb 25, 2016
@dhermes dhermes deleted the happybase-finish-batch branch February 25, 2016 23:40
parthea pushed a commit that referenced this pull request Nov 26, 2025
…easier time pinning the correct OpenSSL version. (#1537)

* chore: Use cryptography for the Provider as well. This is to have an easier time pinning the correct OpenSSL version.
parthea pushed a commit that referenced this pull request Mar 6, 2026
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
parthea added a commit that referenced this pull request Mar 6, 2026
#1541)

* bug: fixes discrepancy btwn python-api-core & bigquery re object default timeout

* Fix: loosen ipywidget dependency (#1504)

* fix: updates ipywidget dependency

* fix: updates ipywidget version number

* chore(main): release 3.6.0 (#1490)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

* docs: Remove < 3.11 reference from README (#1502)

* chore(python): upgrade gcp-releasetool in .kokoro [autoapprove] (#1508)

Source-Link: googleapis/synthtool@5f2a608
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:8555f0e37e6261408f792bfd6635102d2da5ad73f8f09bcb24f25e6afb5fac97

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* feat: add `connection_properties` and `create_session` to `LoadJobConfig` (#1509)

* feat: added `connection_properties` and `create_session` in load job

* chore(deps): update all dependencies (#1501)

* chore(deps): update all dependencies

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Anthonios Partheniou <partheniou@google.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* chore(deps): update all dependencies (#1513)

* feat: add default_query_job_config property and property setter to BQ client (#1511)

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:
- [x] Make sure to open an issue as a [feature request](https://togithub.com/googleapis/python-bigquery/issues/1512) before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)

Fixes 
- [feature request](https://togithub.com/googleapis/python-bigquery/issues/1512)🦕
- [internal bug](https://b.corp.google.com/issues/271044948)

* chore(deps): update all dependencies (#1514)

* chore(deps): update dependency charset-normalizer to v3.1.0 (#1518)

* chore(main): release 3.7.0 (#1507)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

* feat: expose configuration property on CopyJob, ExtractJob, LoadJob, QueryJob (#1521)

* feat: expose configuration property on CopyJob, ExtractJob, LoadJob, QueryJob

Note for google-cloud-bigquery developers: This also refactors these classes so
that `_set_properties` does not modify the `_properties` dictionary in-place.
Doing so was also mutating the request object, making it difficult to debug
what request was _actually_ sent. Before this change, many tests hallucinated
that the request was always equal to the response.

* E           google.api_core.exceptions.BadRequest: 400 Clone operation with write disposition WRITE_TRUNCATE is not supported. Please try again with WRITE_EMPTY.

* chore(deps): Update nox in .kokoro/requirements.in [autoapprove] (#1527)

Source-Link: googleapis/synthtool@92006bb
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:2e247c7bf5154df7f98cce087a20ca7605e236340c7d6d1a14447e5c06791bd6

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* feat: add default LoadJobConfig to Client (#1526)

* feat: add bool, int, float, string dtype to to_dataframe (#1529)

* fix: loosen ipywidgets restrictions further to address ipython compatibility issues (#1531)

* fix: loosen ipywidgets restrictions further to address ipython compatibility issues

* include ipywidgets in prerelease deps

* show all package versions

* add ipykernel dependency

* ipykernel in noxfile

* oops

* chore(main): release 3.8.0 (#1525)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

* fix: keyerror when the load_table_from_dataframe accesses a unmapped dtype dataframe index (#1535)

* feat: expose query job on dbapi cursor (#1520)

Co-authored-by: Tim Swast <swast@google.com>

* chore(main): release 3.9.0 (#1537)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

* chore: update tests to be compatible with pandas 2.0 (#1538)

* chore: update tests to be compatible with pandas 2.0

* use StringDtype without storage argument

* avoid Float64Dtype on older pandas

* chore(deps): update all dependencies (#1522)

* chore: updates minimum version of bqstorage (#1542)

* chore: updates minimum version of bqstorage

* removes unneeded test

* updates linting, removes unneeded comment

* updates conditional checks, comments, adds test

* Removes test, adds pragma no cover

* Removes test

* fix linting error

---------

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Atsushi Yamamoto <yamaatsushi927@gmail.com>
Co-authored-by: gcf-owl-bot[bot] <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Shobhit Singh <just.shobhit@gmail.com>
Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: Anthonios Partheniou <partheniou@google.com>
Co-authored-by: chelsea-lin <124939984+chelsea-lin@users.noreply.github.com>
Co-authored-by: Tim Swast <swast@google.com>
Co-authored-by: r1b <robert.cole.jensen@gmail.com>
parthea pushed a commit that referenced this pull request Mar 9, 2026
* feat(experimental): add async grpc client

* minor changes

* remove unused import

* update the imports for _storage_v2

* change the default directpath value to True

* add more comprehensive unit tests

* adding helper methods
parthea pushed a commit that referenced this pull request Mar 31, 2026
…#1537)

**Problem**
Following the introduction of AsyncIO support via CrossSync, code
generation for the synchronous client caused a regression in
Database.database_dialect.

Previously, if the property was accessed and returned
DATABASE_DIALECT_UNSPECIFIED, the client would implicitly make a
blocking self.reload() to retrieve the dialect from the server. This was
lost during the shift to CrossSync as properties cannot be asynchronous
in the _async source of truth.

**Solution**
Restore the lazy-loading reload behavior via an environment check:

__async/database.py_: Added if not CrossSync.is_async: guard directly
into the database_dialect getter. This makes it un-reachable code in the
async runtime (where blocking properties or un-awaited coroutines are
frowned upon).
_database.py_: The generator strips the CrossSync context into a
standard synchronous self.reload() call, successfully maintaining strict
backwards compatibility for all existing synchronous libraries.
parthea pushed a commit that referenced this pull request Apr 1, 2026
PR created by the Librarian CLI to initialize a release. Merging this PR
will auto trigger a release.

Librarian Version: v0.0.0-20260331223231-14b1b9186e21
Language Image:
us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:234b9d1f2ddb057ed7ac6a38db0bf8163d839c65c6cf88ade52530cddebce59e
<details><summary>google-cloud-spanner: v3.64.0</summary>

##
[v3.64.0](google-cloud-spanner-v3.63.0...google-cloud-spanner-v3.64.0)
(2026-04-01)

### Features

* use inline begin to eliminate BeginTransaction RPC (#1502)
([00d5f8e6](00d5f8e6))

* add TLS/mTLS support for experimental host (#1479)
([0c4c5da](0c4c5da3))

* add Client Context support to options (#1499)
([0da5f78](0da5f785))

* Exposing total CPU related fields in AutoscalingConfig
(PiperOrigin-RevId: 845819318)
([9d2338a](9d2338a6))

* include cache updates into the ResultSet response (PiperOrigin-RevId:
865546011)
([9d2338a](9d2338a6))

* add a ClientContext field to Spanner requests (PiperOrigin-RevId:
853323071)
([9d2338a](9d2338a6))

* include cache updates and routing hint into BeginTransaction and
Commit request/response respectively (PiperOrigin-RevId: 878019893)
([9d2338a](9d2338a6))

* add Secure Parameters to the ClientContext (PiperOrigin-RevId:
853323071)
([9d2338a](9d2338a6))

* implement native asyncio support via Cross-Sync (#1509)
([f822fd7](f822fd7c))

### Bug Fixes

* add threading import and _resource_info to snapshot.py
([659034a](659034aa))

* restore implicit database_dialect reload in sync client (#1537)
([67f5104](67f51043))

* resolve async deadlock in multiplexed session manager (#1520)
([c8f936b](c8f936b0))

### Documentation

* mark new AsyncIO APIs as experimental (#1533)
([3909c04](3909c045))

* A comment for field `transaction_tag` in message
`.google.spanner.v1.RequestOptions` is changed (PiperOrigin-RevId:
865546011)
([9d2338a](9d2338a6))

* A comment for field `routing_hint` in messages
`.google.spanner.v1.ResultSet` and `.google.spanner.v1.PartialResultSet`
are changed (PiperOrigin-RevId: 878019893)
([9d2338a](9d2338a6))

* Update high_priority_cpu_utilization_percent in AutoscalingConfig to
be Optional and clarify its behavior when not specified
(PiperOrigin-RevId: 845819318)
([9d2338a](9d2338a6))

* A comment for field `params` in message
`.google.spanner.v1.PartitionQueryRequest` is changed
(PiperOrigin-RevId: 865546011)
([9d2338a](9d2338a6))

* A comment in message
`.google.spanner.v1.TransactionOptions.ReadWrite.ReadLockMode` is
changed (PiperOrigin-RevId: 878019893)
([9d2338a](9d2338a6))

* A comment for field `commit_timestamp` in message
`.google.spanner.v1.BatchWriteResponse` is changed (PiperOrigin-RevId:
865546011)
([9d2338a](9d2338a6))

* minor update for Spanner Location API (PiperOrigin-RevId: 834841888)
([9d2338a](9d2338a6))

* A comment for field `param_types` in message
`.google.spanner.v1.PartitionQueryRequest` is changed
(PiperOrigin-RevId: 865546011)
([9d2338a](9d2338a6))

</details>
parthea pushed a commit that referenced this pull request Apr 1, 2026
…e account explicit (#1537)

* feat!: make `remote_function` default service account explicit

chore!: make `remote_function` params keyword only

* pass cloud_function_service_account="default" in unit tests

* pass default cloud_build_service_account in the doctests

* pass default cloud_function_service_account in the samples

* pass cloud_function_service_account="default" to the read_gbq_function doctest

* use cloud_function_service_account="default" at more places

* remove positional argument usage for remote_function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigtable Issues related to the Bigtable API. cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants