Skip to content

Conversation

@tseaver
Copy link
Contributor

@tseaver tseaver commented Feb 16, 2015

Step #2 in #15 (comment)

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Feb 16, 2015
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 5fed4d2 on tseaver:15-add_storage_batch into * on GoogleCloudPlatform:master*.

@tseaver
Copy link
Contributor Author

tseaver commented Feb 16, 2015

@craigcitro, @dhermes I'm willing to do the work to vendor in and use the apitools batch module, if Craig doesn't think it will have a PyPI release soon. I can also work on getting it up-to-speed in terms of test coverage and Py3k straddling in the canonical repository, if that would help.

@dhermes
Copy link
Contributor

dhermes commented Feb 17, 2015

Should I review this or rely on the vendored in code?

@tseaver
Copy link
Contributor Author

tseaver commented Feb 17, 2015

@dhermes we don't have a vendored-in version of that module yet. My earlier question was whether we should go ahead and vendor that code in, given that it has no coverage and does not straddle Py3k yet.

The amount of code in the new storage/batch.py module which would be replaced if we chose to vendor the apitools module is relatively small (135 out of 544 lines):

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling ae0e9cf on tseaver:15-add_storage_batch into 8e68a20 on GoogleCloudPlatform:master.

@dhermes dhermes added the api: storage Issues related to the Cloud Storage API. label Feb 18, 2015
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6261272 on tseaver:15-add_storage_batch into 8e68a20 on GoogleCloudPlatform:master.

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.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling af2a382 on tseaver:15-add_storage_batch into 8e68a20 on GoogleCloudPlatform:master.

A batch proxies a connection, deferring write requests.
In preparation for making 'storage.batch.Batch' derive from Connection,
allowing it to override only the actual transmission of the HTTP request.
Drop patching the connection's 'http', as well as proxying its attributes
(we get that via subclassing).
@tseaver
Copy link
Contributor Author

tseaver commented Feb 25, 2015

@dhermes PTAL.

Rebased on top of master, squashing all previous commits; then implemented subclassing per our discussion today.

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.

@dhermes
Copy link
Contributor

dhermes commented Feb 26, 2015

RE: #654 (comment)

@craigcitro can we help get apitools:

  • In PyPI
  • Supporting Py3
  • Merging upstream changes from places like gsutil

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@craigcitro
Copy link
Contributor

replying to myself for posterity: i believe neither uploads nor downloads work in a batch.

@craigcitro
Copy link
Contributor

@dhermes yes! so here's the current apitools plan:

  • i'm working on merging the gsutil fork today
  • once i do that, i'm going to submit to pypi
  • after that, help getting it py3 ready would be AWESOME
  • even right now, py3 support for protorpc would be super

The batching interface is not specific to the storage API.
It does not case-normalize header key lookup, but stores headers only
as lowercase.
@dhermes
Copy link
Contributor

dhermes commented Feb 26, 2015

For posterity (RE: Craig's comment):

Note: Currently, Google Cloud Storage does not support batch operations for
media, either for upload or download.

screen_shot_074

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling de6fd48 on tseaver:15-add_storage_batch into 808c38b on GoogleCloudPlatform:master.

@dhermes
Copy link
Contributor

dhermes commented Feb 26, 2015

I think everything looks good except removing that unused sys import.

LGTM

@dhermes
Copy link
Contributor

dhermes commented Feb 26, 2015

@craigcitro Can we start a new issue to discuss apitools / protorpc? Should the issue be here or in one (or both) of those repos?

@craigcitro
Copy link
Contributor

@dhermes yeah, new issue wherever sgtm. maybe a "py3 support" issue in each of protorpc/apitools, and an issue here for "better apitools dependency" blocked by those two?

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c828bda on tseaver:15-add_storage_batch into d43c4a0 on GoogleCloudPlatform:master.

tseaver added a commit that referenced this pull request Feb 26, 2015
@tseaver tseaver merged commit f0a1157 into googleapis:master Feb 26, 2015
@tseaver tseaver deleted the 15-add_storage_batch branch February 26, 2015 19:10
@dhermes
Copy link
Contributor

dhermes commented Apr 9, 2015

@tseaver We discussed using the apitools batch support when this went in. We should discuss if / how that's possible (in light of #811).

parthea pushed a commit that referenced this pull request Nov 24, 2025
…#654)

This was noticed when attempting to generate Bigtable Admin in a
message definition: an imported module is given an alias to prevent
collision with a field name. When the module is referenced to describe
the type of a singleton field it is properly disambiguated. When used
to describe the type of a MapField it is _not_ disambiguated.

Fix for that.

Closes #618
parthea pushed a commit that referenced this pull request Nov 24, 2025
It turns out this was unnecessary and can cause problems of its own.

Fixes #649 #634
parthea pushed a commit that referenced this pull request Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: storage Issues related to the Cloud Storage API. cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants