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
Bulk API #371
Comments
Bulk API, closed by 3afe4da. |
In the example, the "index" and "create" lines have a missing } at the end of the line. |
thanks, fixed. |
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…l request elastic#371) MPC-4110: explicit permission for eventbridge rules to run lambda functions * explicit permission for eventbridge rules to run lambda functions Approved-by: Can Yildiz
costin
pushed a commit
that referenced
this issue
Dec 6, 2022
This adds a logical optimizer rule to push down the filters as much as possible. Cases where this can't be done are those where the conditions are making use of the output of aggregations or the fields define in eval. A filter rewriting rule, substituting eval's attributions in the filter and re-evaluating the filter for push'ability isn't considered here. Part of #338.
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
by default this task fails in lowmem env due to the presence of loopback devices in lowmem-rally-2. this change excludes loopback devices from trickling down to smartctl checks.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expose bulk API for indexing and deleting docs. The REST AP endpoint is
/_bulk
and it follows the following structure (for json):for example:
A note on the format. The idea here is to make processing of this as fast as possible. As some of the actions will be needed to be redirected to other shards that exists on other nodes, only the action meta_data is parsed on the receiving node side. Also, zero copy buffers can be used on the source directly writing segments relevant to each action source to the network.
Client libraries using this protocol should try and strive to do something similar on the client side, and reduce as much as possible the creation of buffers.
The result is a full formatted json, with all the actions performed (in the same order), with possible error field indicating for each one in case of failure (on an item level).
Note, in the end, the full data needs to be represented on each server, so indexing 5GB of data should be broken down and not executed in a single batch.
If using the HTTP API, make sure that the client does not send HTTP chunks, as this will slow things down.
The text was updated successfully, but these errors were encountered: