-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Port Datastore onto GAPIC #2746
Comments
@bjwatson Two questions:
|
@dhermes Only because @geigerj says that he needs to make some small updates to the GAPIC generator for it to be compatible with I thought I would get this in your hands right away, rather than waiting for the necessary fixes to support the newer auth helpers. However, if you think it's a more efficient use of your time to wait, then we can do that. |
@bjwatson Sorry I didn't notice this until now, but the current form of Right now we support Protobuf-over-HTTP and Protobuf-over-gRPC, so we need access to the protobuf classes in use cases where gRPC isn't available (i.e. App Engine). The generated protobuf classes currently live in /cc @jonparrott |
@dhermes Does googleapis/api-client-staging@6649c45 do what you need? Do you also need changes to Note that this will become unnecessary once grpc/grpc#8056 is released in |
Yes it does do what I had in mind. We had conditional checks in our AFAIK, even though |
|
@bjwatson Ping me once released? |
@bjwatson Is this a Datastore-specific hand-edit, or do we intend to provide these conditional imports across the gRPC packages we maintain? If it's the latter, we should figure out what the timeline for |
@geigerj @bjwatson We would love to see a new release of |
@dhermes We're going to wait on porting Datastore to GAPIC until after the beta announcement. We discussed and we don't want to take any chances on destabilizing the |
SGTM |
Towards googleapis#2746. This approach is to slowly transition from our current approach to use the GAPIC generated surface. It is unfortunately tangled quite a bit (partly because we may have too much mocked in the tests).
Towards googleapis#2746 (as is googleapis#3064). This approach is to slowly transition from our current approach to use the GAPIC generated surface. These unit tests weren't so bad to update. I did "editorialize" as I went, downgrading constants to just variables, renamining for PEP8, etc.
Towards googleapis#2746. This approach is to slowly transition from our current approach to use the GAPIC generated surface. It is unfortunately tangled quite a bit (partly because we may have too much mocked in the tests).
@lukesneeringer @dhermes If we're blocking the |
Ok, thanks Danny! |
This is to prepare for a removal of the Connection class (relates to googleapis#2746 and googleapis#3105).
This is progress towards googleapis#2746 and makes Connection() act as a proxy for the contents of Client (as intended).
This is progress towards googleapis#2746 and makes Connection() act as a proxy for the contents of Client (as intended).
This is progress towards googleapis#2746 and makes Connection() act as a proxy for the contents of Client (as intended).
@dhermes This is now done, question mark? |
Almost. One follow-up PR, coming in hot. |
Woo hoo! Great job, Danny! @lukesneeringer @dhermes Does this mean that we'll have the new HTTP headers working for Datastore as soon as this is published? |
I believe we have the HTTP headers now. But, yes. |
I just did a
and the only change that is in the public interface is the addition of |
Sure, but it is a huge under-the-hood change, because those with GRPC support are suddenly using the GRPC transport now. |
@lukesneeringer We already had the gRPC transport (for many releases), it was just the raw stub produced by the |
Okay. |
Towards googleapis#2746 (as is googleapis#3064). This approach is to slowly transition from our current approach to use the GAPIC generated surface. These unit tests weren't so bad to update. I did "editorialize" as I went, downgrading constants to just variables, renamining for PEP8, etc.
Towards googleapis#2746. This approach is to slowly transition from our current approach to use the GAPIC generated surface. It is unfortunately tangled quite a bit (partly because we may have too much mocked in the tests).
This is to prepare for a removal of the Connection class (relates to googleapis#2746 and googleapis#3105).
This is progress towards googleapis#2746 and makes Connection() act as a proxy for the contents of Client (as intended).
What
Port the gRPC code path for Datastore onto GAPIC. The package is available here.
Why
This is not a beta-blocker, since there already is gRPC code for Datastore, but it is preferred.
The text was updated successfully, but these errors were encountered: