Skip to content
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

Force date format in context query #22684

Merged
merged 2 commits into from
Sep 7, 2018

Commits on Sep 4, 2018

  1. Force date format in context query

    Fixes issue reported in https://discuss.elastic.co/t/view-surrounding-documents-causes-failed-to-parse-date-field-exception/147234
    
    The default date field format is `strict_date_optional_time||epoch_millis`
    so we didn't run into this during testing. If the user has custom
    mappings for their timestamp field and `epoch_millis` isn't one of the
    optional formats the context query will fail since it always sends the
    date in millis. This change forces the query to accept the date in millis.
    Bargs committed Sep 4, 2018
    Configuration menu
    Copy the full SHA
    4f5d6bd View commit details
    Browse the repository at this point in the history

Commits on Sep 5, 2018

  1. Update tests

    Bargs committed Sep 5, 2018
    Configuration menu
    Copy the full SHA
    e5410d7 View commit details
    Browse the repository at this point in the history