Search fails when sorting on a field that has no values in the hits returned #285
Comments
|
Search fails when sorting on a field that has no values in the hits returned, closed by dfb68c6. |
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
Add option to limit the number of replays of a failing tuple and also what to do in case of no more attempts Fix elastic#285
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…lastic#285) Packer: add support for building ems image on linode * Add `--builder` option. Defaults to AWS, aka amazon-ebs (packer builder type), for backward compatibility. * Add `/etc/engageli/hosting.env` file so code on instance could detect the type of hosting. * To avoid having to give the packer instance AWS keys, the EMS TGZ is downloaded to local, the uploaded by packer's "file" provisioner. Approved-by: Can Yildiz Approved-by: Andre Sodermans
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When executing a search with sorting on a specific string field, and that field has no values in all the hits matched / returned, search will fail.
The text was updated successfully, but these errors were encountered: