-
Notifications
You must be signed in to change notification settings - Fork 636
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
Respond correctly when batch appending idempotent write to deleted stream (DB-535) #4059
Respond correctly when batch appending idempotent write to deleted stream (DB-535) #4059
Conversation
…ream Before this fix the null value here resulted in a NRE when sending the proto message
DB-535 Idempotent write to deleted stream throws exception when appending with batch append
Repro with dotnet client 23.1.0
results in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timothycoleman 👉 Created pull request targeting release/oss-v22.10: #4077
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timothycoleman 👉 Created pull request targeting release/oss-v23.10: #4078
Fixed: 'Unknown' error reported to client after successful idempotent write to deleted stream.
Before this fix the null value here resulted in a NRE when sending the proto message.
The server did correctly identify that the write was idempotent and not append any more events. The IndexWriter then returns -1 as the position of the existing event because it is deleted, and this was not being correctly represented in the batch append proto message.
#4058