-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Search with sort field of score fails #83
Comments
This seems to be the cause of the bad total values too - some shards fail, and the returned hits are less than estimated: Try this script - i add various docs, do a search on both nodes, sleep, repeat the search, add another doc and repeat the search:
|
Fixed, can you verify? |
Fixed+++ Sheer genius :) |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Closes #83. (cherry picked from commit 67ac149)
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
As seen with elastic#7474, we need to update mapper attachment plugin with this new signature. Closes elastic#83.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Merged debian init script changes from elasticsearch
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we remove a few challenges that were created for specific investigations reducing the complexity of this track. Closes elastic#74
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we get rid of all string-based representation of more complex parameters. This affects track-params and car-params specifically which will now be passed to Rally as JSON string in any case. This allows to merge those parameters in more complex scenarios where we need to source them from multiple places. Closes elastic#82 Relates elastic#83
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
I've managed to replicate the RemoteTransportException that doesn't include the actual exception.
Start two nodes on localhost, then run this script:
The text was updated successfully, but these errors were encountered: