You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
varrequest = newClientWriteRequest()
.writes(List.of(
newClientTupleKey()
.user("user:81684243-9356-4421-8fbf-a4f8d36aa31b")
.relation("viewer")
._object("document:roadmap"),
newClientTupleKey()
.user("user:81684243-9356-4421-8fbf-a4f8d36aa31b")
.relation("viewer")
._object("document:budget")
));
varoptions = newClientWriteOptions()
.disableTransactions(true)
.transactionChunkSize(1); // Maximum number of requests to be sent in a transaction in a particular chunkvarresponse = fgaClient.write(request, options).get();
OpenFGA SDK version
v0.5.0
OpenFGA version
N/A
SDK Configuration
N/A
Logs
No response
References
No response
The text was updated successfully, but these errors were encountered:
rhamzeh
changed the title
In the non-Txn Write, we should be catching the errors and wrapping them before sending it to the server
In the non-Txn Write, we should be catching the errors and wrapping them
Aug 7, 2024
Checklist
Description
In the non-txn Write, we should not error if a single tuple had a validation error
https://github.com/openfga/java-sdk/blob/b1e03e523c530824f5921313c2191dc5f6d93af8/src/main/java/dev/openfga/sdk/api/client/OpenFgaClient.java#L427C34-L427C99
Expectation
We should match what the other SDKs are doing, e.g.
Catching the response if failed and setting
status: ClientWriteStatus.FAILURE
for the individual failed tuplesReproduction
Have the following tuple already written
and then do:
OpenFGA SDK version
v0.5.0
OpenFGA version
N/A
SDK Configuration
N/A
Logs
No response
References
No response
The text was updated successfully, but these errors were encountered: