Fix unstable WRITE when first write fails to open file #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If something goes wrong on unstable
WRITE
when opening the file (Access Denied because it's flagged read-only on server side fo example), a NULL entry is still stored inunstableStorageFile
. This cause any futureWRITE
calls to the same file to always fail, becauseCOMMIT
may not be invoked by the client.This PR fix this issue by storing file pointer in
unstableStorageFile
only if not NULL.