-
Notifications
You must be signed in to change notification settings - Fork 25.2k
API Change: search sort #113
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
Labels
Comments
Going to support it as well as the old way |
implemented |
Tested++ |
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
Some exceptions might not be serializable. It would be safer not to wrap them in a `MapperParsingException` but just create the `MapperParsingException`. Related to elastic#113. (cherry picked from commit e58878c) (cherry picked from commit a673185)
This was referenced Mar 14, 2022
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we add the machine information for the new nightly environment and also clarify that the definitive reference is not this list but rather our SSH configuration. Relates elastic#113
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of specifying sort order like this:
"sort" : [
"name",
{
"last_modified" : {
"reverse" : 1
}
}
],
What about like this?
"sort" : [
"name",
{"last_modified" : "desc"}
],
or
When you sort on
score
,reverse: true
impliesasc
, but for everything else,reverse: true
impliesdesc
. So why not make it unambiguous?The text was updated successfully, but these errors were encountered: