-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] GetSourceRequest has unnecessary field _source #283
Comments
Could fixing this break someone's working code? If so, we might want to put this change into the 3.x line. |
Yes, it may affect the end user code. So, we can already commit into the 3.x line? |
Is there a way to fix this that preserves working code? |
I think not, since we will remove the source field from the structure, those clients who already have this field in the structure (even if it does not carry functionality) will receive an syntax error. Therefore, it is better to plan for future versions. |
Can we deprecate this parameter in the next version and then remove in the next major version? |
Yes, why not. If we fix it in this version it will break everything, it's best to plan for the next version |
@zethuman I was looking at this and looks like the
The response was So the code needs to be fixed rather than _source parameter removed entirely. I will raise a PR soon for this. |
It is however similar to |
What is the bug?
The field _source is not needed, since this parameter has no functionality, since only the option is available -
true
How can one reproduce the bug?
Input:
Output:
{[{action_request_validation_exception Validation Failed: 1: fetching source can not be disabled; }] action_request_validation_exception Validation Failed: 1: fetching source can not be disabled; }
What is the expected behavior?
Default option is
true
logically there must be option withfalse
. Expected to does not include the _source field in the response body.What is your host/environment?
MacOS Ventura / opensearchproject/opensearch:latest / Go 1.15
Possible solution
I can remove this one, since it is not logical to be able to pass a negative value in a request whose purpose is to receive this data.
The text was updated successfully, but these errors were encountered: