SOLR-18439: v2 APIs use 200 on success and 500 with a error.msg key - #4899
Open
epugh wants to merge 3 commits into
Open
SOLR-18439: v2 APIs use 200 on success and 500 with a error.msg key#4899epugh wants to merge 3 commits into
epugh wants to merge 3 commits into
Conversation
…v2 apis into alignment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://issues.apache.org/jira/browse/SOLR-18439
Description
We have a standard on V2 apis that 200 is success and 500 is an error, with a message under
error.msgattribute. Most of the API's have that, but some don't so bring them into compliance.Solution
Update three apis. They aren't used yet by any existing code, and haven't been released in Solr, so I think we don't need a changelog.