Skip to content

Handling datastore renames on Query and QueryResultBatch. - #1357

Closed
dhermes wants to merge 3 commits into
googleapis:masterfrom
dhermes:query-renames-1288
Closed

Handling datastore renames on Query and QueryResultBatch.#1357
dhermes wants to merge 3 commits into
googleapis:masterfrom
dhermes:query-renames-1288

Conversation

@dhermes

Copy link
Copy Markdown
Contributor

Can't be merged until v1beta3 is released.

@dhermesdhermes added api: datastore Issues related to the Datastore API. do not merge Indicates a pull request not ready for merge, due to either quality or timing. labels Jan 7, 2016
@googlebotgooglebot added the cla: yes This human has signed the Contributor License Agreement. label Jan 7, 2016
@dhermesdhermes mentioned this pull request Jan 7, 2016
49 tasks
@dhermesdhermes closed this Feb 12, 2016
@dhermes
dhermes deleted the query-renames-1288 branch February 12, 2016 22:31
parthea pushed a commit that referenced this pull request Mar 6, 2026
* tests some options
* refactors to use tqdm.* notation
* refactors tqdm function calls to account for deprecation warning
* refactors _tqdm_helpers to account for tqdm deprecation warnings
* 🦉 Updates from OwlBot post-processor
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md
* removes an extraneous reference to ipywidgets
* removes unneeded import
* removes import and fixes linting error
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Mar 9, 2026
…nloading using transfer_manager (#1357)
* fix: do not spam the log with checksum related INFO messages when downloading using transfer_manager
`download_chunks_concurrently` function does not allow to set `checksum` field in `download_kwargs`. It also does not set it on its own so it takes the default value of `"md5"` (see `Blob._prep_and_do_download`). Because ranged downloads do not return checksums it results in a lot of INFO messages (tens/hundreds):
```
INFO google.resumable_media._helpers - No MD5 checksum was returned from the service while downloading ...
(which happens for composite objects), so client-side content integrity checking is not being performed.
```
To fix it set the `checksum` field to `None` which means no checksum checking for individual chunks. Note that `transfer_manager` has its own checksum checking logic (enabled by `crc32c_checksum` argument)
* fix tests
parthea pushed a commit that referenced this pull request Mar 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: datastoreIssues related to the Datastore API.cla: yesThis human has signed the Contributor License Agreement.do not mergeIndicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@dhermes@googlebot