-
Notifications
You must be signed in to change notification settings - Fork 25k
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
query.sort should be an array, not an object #30
Comments
Have you seem somewhere that JSON doesn't take order into account? All the parsers that I have seen, for example, do create a linked hash map to represent an object, which means order is maintained. Of course, I don't convert the JSON into "nodes" or maps, but use pull parsing instead, but I still take order into account. In any case, I agree that the format you mentioned is more coherent. I will add support for that (and the old format as well :) ). |
Allow for the sort search element to speciy the sort fields in an array, closed by 1aa8e01. |
To be honest, no I hadn't - but I've found this post which discusses the issue http://pmuellr.blogspot.com/2009/04/ordered-javascript-properties.html. In Perl, hashes (the equivalent structure) are unordered, so I'm glad you're happy to add support for the array form :) |
Excellent - I can confirm that this is working |
If the AWS client throws an exception (e.g: because of a DNS failure) it will end up killing the rejoin thread and stop retrying which can lead to a node getting stuck unable to rejoin the cluster. Closes #30.
Closes #30. (cherry picked from commit bf7cc95)
Closes #30. (cherry picked from commit fad6ebf)
In certain environments (such as inside a docker container) 'metadata' does not resolve. Forcing URL to `http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token` fix this. See https://developers.google.com/compute/docs/metadata#metadataserver Closes #28. Closes #30.
Related to #30 (cherry picked from commit 442d06e) (cherry picked from commit aa27eb9)
Previously, we tracked any active publication, and associated timeout, using the PUBLISH_IN_PROGRESS leader mode. This change introduces a separate timeout for publication and tracks it using the FutureExecutor instead.
Added functionality to copy elasticsearch scripts
* Added parameter for addressing frozen indices * Added frozen challenges * Increased generated data volume and reduces data volume queried * Added pre_filter_shard_size parameter to Kibana queries when querying frozen indices * Corrected query string config * Corrected fieldstats runner * Corrected kibana runner * Added debug parameter for kibana simulation * Added debug parameter for kibana simulation * Added IP filter to dashboards to make queries lighter * Altered format of debug output * Added frozen status to debug output * Moved frozen handling to parameter source query generation * Made frozen querying lighter * Enable fieldstats runner to handle frozen indices * Modified frozen querying parameters and added ability to use track parameters * Cleaned up code and docs
Because JSON doesn't take order into account, sort should be an array, not an object.
For instance:
sort : {
postDate : {reverse : true},
user : { },
score : { }
}
is the equivalent of:
Instead, perhaps this syntax:
clint
The text was updated successfully, but these errors were encountered: