We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Base REST handler tracks consumed parameters and content.
When a param is required, and is not consumed (via request.param("foo")) the Base Rest Handler overrides whatever message is returned to OpenSearch.
request.param("foo")
{ "error": { "root_cause": [ { "type": "illegal_argument_exception", "reason": "request [/_plugins/_flow_framework/workflow/foobar] contains unrecognized parameter: [workflow_id]" } ], "type": "illegal_argument_exception", "reason": "request [/_plugins/_flow_framework/workflow/foobar] contains unrecognized parameter: [workflow_id]" }, "status": 400 }
The specific error message produced by the API (for example, the need to enable the feature flag).
The fix is to consume the param prior to any attempted rest response, for example:
String workflowId = request.param("workflow_id");
This is a similar error to #274 but more critical to fix (thus BUG instead of FEATURE). Both this bug and #274 can/should be fixed at the same time.
The text was updated successfully, but these errors were encountered:
dbwiddis
Successfully merging a pull request may close this issue.
What is the bug?
The Base REST handler tracks consumed parameters and content.
When a param is required, and is not consumed (via
request.param("foo")
) the Base Rest Handler overrides whatever message is returned to OpenSearch.How can one reproduce the bug?
What is the expected behavior?
The specific error message produced by the API (for example, the need to enable the feature flag).
Do you have any additional context?
The fix is to consume the param prior to any attempted rest response, for example:
This is a similar error to #274 but more critical to fix (thus BUG instead of FEATURE). Both this bug and #274 can/should be fixed at the same time.
The text was updated successfully, but these errors were encountered: