-
Notifications
You must be signed in to change notification settings - Fork 101
Add Search Applications API #2080
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
Add Search Applications API #2080
Conversation
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.
Looks great, thanks for doing this @carlosdelest ! One comment.
"responseMediaType": [ | ||
"application/json" | ||
], | ||
"since": "8.8.0", | ||
"stability": "beta", |
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 think we need to change the stability of search applications from beta to tech preview right?
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 was thinking on having first input from the clients team - we need to do that change in the ES specs as well so it gets propagated here. Thanks for the reminder!
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.
The API docs have already been updated! elastic/elasticsearch#95308
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.
Looks good to me, only had one comment:
*/ | ||
name: Name | ||
} | ||
/** @codegen_name search_params */ |
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.
If the fields in the request body are parameters in their own right (rather than say, a model definition) then you don't need a codegen_name
here. Having a @codegen_name
for the body
will treat the entire body as one parameter, rather than the individual fields in the body as parameters.
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.
Thanks @sethmlarson ! There were validation errors that pointed to using codegen_name
so I included that. Removing this!
Closing this PR to open from the same repo, so Github actions are successful |
Add Search Applications API, including both CRUD and
_search
request.