Skip to content
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

fix: correctly handle MaxSeriesPerDatabaseExceeded (#23091) #23093

Merged
merged 1 commit into from
Feb 2, 2022

Conversation

davidby-influx
Copy link
Contributor

Check for the correctly returned PartialWriteError
in (*shard).validateSeriesAndFields, allow partial
writes.

closes #23090

(cherry picked from commit 0c3dca8)

closes #23092

Check for the correctly returned PartialWriteError
in (*shard).validateSeriesAndFields, allow partial
writes.

closes #23090

(cherry picked from commit 0c3dca8)
@davidby-influx davidby-influx merged commit 85580fa into 1.9 Feb 2, 2022
@davidby-influx davidby-influx deleted the DSB_series_max_1.9 branch February 2, 2022 05:51
// Maybe we can just change it to be consistent if we change it also in all
// the places that construct it.
// (DSB) This was previously *PartialWriteError. Now catch pointer and value types.
case PartialWriteError:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a test that shows this? I think both of the existing tests were already returning the right error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both previous code and new code return the same error string, but new code actually completes the partial write as much as possible, instead of turning into a complete failure. I will look to see if there's a reasonable way to verify the partial success in actual data written.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Correctly handle MaxSeriesPerDatabaseExceeded PartialWriteError [port to 1.9]
3 participants