-
Notifications
You must be signed in to change notification settings - Fork 108
Update rest-api-spec main #4831
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
Conversation
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
/** | ||
* Whether vectors should be excluded from _source | ||
* @availability stack since=9.2.0 | ||
* @availability serverless | ||
* @server_default false | ||
*/ | ||
_source_exclude_vectors?: boolean |
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.
@jimczi My understanding is that those query parameters are not behind a feature flag, only the new mappings are. So the query parameter will end up in 9.2.0 and Serverless. Is that correct?
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.
Yes that's correct.
/** | ||
* Filter out results, for example to filter out sensitive information. Supports wildcards or full settings keys | ||
*/ | ||
settings_filter?: string | string[] |
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 considered Names
instead but @Anaethelion tells me that it's safer to start from an union and maybe move to Names
or another similar type alias later.
As titled.