-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Mark the search 'fields' option as beta. #63699
Conversation
Pinging @elastic/es-docs (>docs) |
Pinging @elastic/es-search (:Search/Search) |
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.
Makes sense to me! Hopefully we won't end up breaking the API to handle those issues but it is important that we have the option if we need it. And we have a plan for removing this - once we've got those two issues handled we can remove this.
Thanks @nik9000 ! |
We've identified two important enhancements that may affect the API. We expect any API changes from these enhancements to be minor, but want to leave open the possibility for small breaks. For example, we may end up returning unmapped fields by default, or omitting nested fields from the root hit. The impact to users should be quite small. We're tracking the issues we need to resolve before removing the 'beta' label here: #60985.
We've identified two important enhancements that may affect the API. We expect any API changes from these enhancements to be minor, but want to leave open the possibility for small breaks. For example, we may end up returning unmapped fields by default, or omitting nested fields from the root hit. The impact to users should be quite small. We're tracking the issues we need to resolve before removing the 'beta' label here: #60985.
We've identified two important enhancements that may affect the API:
We expect any API changes from these enhancements to be minor, but want to leave open the possibility for small breaks. For example, we may end up returning unmapped fields by default, or omitting nested fields from the root hit. The impact to users should be quite small.
We're tracking the issues we need to resolve before removing the 'beta' label here: #60985.