googleapis / googleapis/google-cloud-java

[java-spanner] Possibility to define grpc-timeout dynamically without interacting directly with GrpcCallContext

オープン
#12,262 コメント 3 件 リアクション 0 件 担当者 1 名 @rahul2393 に割り当て済み GitHub で見る
api: spanner
主要言語
Java
スター
2.1k
フォーク
1.2k
平均マージ
1日 23時間
マージ済み PR(30日)
154

説明

Thanks for stopping by to let us know something could be better!

**Is your feature request related to a problem? Please describe.**
My current system receives request from other system which defines deadline/finishby timeout which varies from request type to request type.
I'd like to instruct spanner client to propagate this value to spanner using 'grpc-timeout' header.
Currently it's possible to do this interacting directly with GrpcCallContext via SpannerOptions.CallContextConfigurator.
It would be great to have it as part of SpannerStubSettings, so I don't need to provide my own implementation of SpannerOptions.CallContextConfigurator and attach it to GrpcContext each time it's needed.

**Describe the solution you'd like**
Not sure of what would be the best approach here. I have one idea in mind:
SpannerStubSettings.Builder already contains method applyToAllUnaryMethods(...).
But it's invoked once when settings are build.
applyDynamicallyToAllUnaryMethods(ApiFunction f) method could be introduced which causes invocation of provided ApiFunction on each method invocation (or limit it to specific methods only to move it to UnaryCallSettings level).

**Describe alternatives you've considered**
Currently my system interact with GrpcCallContext directly via SpannerOptions.CallContextConfigurator:

```
public static class SpannerGrpcCallContextConfigurator implements SpannerOptions.CallContextConfigurator {
public ApiCallContext configure(ApiCallContext context, ReqT request,
MethodDescriptor method) {
if (method == SpannerGrpc.getStreamingReadMethod()) {
return GrpcCallContext.createDefault().withCallOptions(CallOptions.DEFAULT.withDeadlineAfter(/*some deadline*/));
}
return null;
}
}
```

then spanner invocation is wrapped with custom grpc context:

```
Context.current()
.withValue(SpannerOptions.CALL_CONTEXT_CONFIGURATOR_KEY, new SpannerGrpcCallContextConfigurator())
.run(() -> { /* spanner invocation here */ });
```

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。