-
Notifications
You must be signed in to change notification settings - Fork 415
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
document search after #4265
document search after #4265
Conversation
c1ef364
to
dcf4de7
Compare
Can you add an example and explain that timestamp must be expressed in nanoseconds? |
docs/reference/es_compatible_api.md
Outdated
@@ -169,7 +169,7 @@ following syntax. | |||
{ | |||
// ... | |||
"sort" : [ | |||
{ "timestamp" : {"order" : "asc"}}, | |||
{ "timestamp" : {"format": "epoch_millis","order" : "asc"}}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
surprise..... I went for epoch_millis_as_int
format as elasticsearch returns milliseconds as strings with format epoch_millis
. Thus I added the ugly as_int
to avoid confusion ://///
{ "timestamp" : {"format": "epoch_millis","order" : "asc"}}, | |
{ "timestamp" : {"format": "epoch_millis_as_int","order" : "asc"}}, |
@@ -353,7 +353,7 @@ fn validate_sort_by_field( | |||
has_timestamp_format: bool, | |||
schema: &Schema, | |||
) -> crate::Result<()> { | |||
if field_name == "_score" { | |||
if ["_score", "_shard_doc", "_doc"].contains(&field_name) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, thank you for fixing this; I totally forgot it.
Do we have tests on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so
Approved, can you just take into account my minor comments? |
Description
fix #4077
I'm not sure what to add more than that line.
somewhat unrelated, document possible improvements to the
partial_request_cache
, that apply particularly to search_after