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 multi percolate api #3488
Labels
Comments
ghost
assigned martijnvg
Aug 12, 2013
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 23, 2014
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 24, 2014
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 24, 2014
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 28, 2014
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 29, 2014
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 29, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The multi percolate allows the bundle multiple percolate requests into one request. This api works similar to the multi search api.
The request body format is line based. Each percolate request item takes two lines, the first line is the header and the second line is the body.
The header can contain any parameter that normally would be set via the request path or query string parameters. There are several percolate actions, because there are multiple types of percolate requests:
percolate
- Action for defining a regular percolate request.count
- Action for defining a count percolate request.Each action has its own set of parameters that need to be specified in the percolate action.
Format:
Depending on the percolate action different parameters can be specified. For example the percolate and percolate existing document actions support different parameters.
The following endpoints are supported:
The
index
andtype
defined in the url path are the default index and type.Example
Request:
The index twitter is the default index and the type tweet is the default type and will be used in the case a header doesn't specify an index or type.
requests.txt:
For a percolate existing document item (headers with the
id
field), the response can be an empty json object. All the required options are set in the header.Response:
Each item represents a percolate response, the order of the items maps to the order in where the percolate requests were specified. In case a percolate request failed, the item response is substituted with an error message.
The text was updated successfully, but these errors were encountered: