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.
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
Optimistic concurrency control for updating ingest pipelines #78551
Optimistic concurrency control for updating ingest pipelines #78551
Changes from 3 commits
4f47288
8c81989
ac8289a
19d60f5
82cc67c
fd15765
1ce0ab9
a10cb40
cd71d7a
dad598b
43f72e0
c9e4163
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think this should be more like an
IllegalArgumentException
, since the required parameter is illegal if there is no pre-existing pipeline?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.
Actually, we do have an exception for something like this, a
VersionConflictEngineException
, which will return back to the userRestStatus.CONFLICT
(a 409), what do you think about using that?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.
That would be great, especially if it resolves the problem with the HTTP error code, but
VersionConflictingEngineException
requires a shard ID and some other index-related values that don't apply to ingest pipelines.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.
@dakrone, I changed the instances of
IllegalStateException
toIllegalArgumentException
in 19d60f5 which I agree better characterizes the problem and is also reported as an HTTP 400 error to the client. Let me know if you think there's a better approach for that.