Repository navigation
etag error code changes in dapr runtime need a change in the sdk #437
Description
Activity
I reproduced this by writing a quick test and as I had expected from the code, the grpc exception gets passed through to the client so there shouldn't be any change required (copied the exception returned below). I'll update the state store example to include this scenario.
Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: ABORTED: failed deleting state with key myKey: possible etag mismatch. error from state store: ERR Error running script (call to f_9b5da7354cb61e2ca9faff50f6c43b81c73c0b94): @user_script:1: user_script:1: failed to delete Maskrazor-Gem||myKey
Expected Behavior
dapr/dapr#2647 changes the error codes returned for etag mismatch and other state api related errors in runtime. Check if java sdk needs a change for this.
Actual Behavior
Dapr runtime used to return the same error code for all state api related errors including etag mismatch.
Steps to Reproduce the Problem
Release Note
RELEASE NOTE: