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.

Sign up for GitHub

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

Jump to bottom

Don't use extended_bounds for time filter in date_histogram #6643

Merged
merged 3 commits into from
Mar 28, 2016
Merged

Don't use extended_bounds for time filter in date_histogram #6643

merged 3 commits into from
Mar 28, 2016

Commits on Mar 24, 2016

  1. Don't use extended_bounds for time filter in date_histogram vis 

    The date histogram vis currently uses extended_bounds on the date_histogram if a time filter is applied which means that these requests can't be cached since the cache key for the request cache for Elasticsearch is based on the request body. The `extended_bounds` here has no effect on the response of the date histogram aggregation because it also sets minDocCount to 0 so will not return any empty buckets.

This change removes the extended bounds parameter for the time filter so these requests can be cached by Elasticsearch.
    @colings86
    colings86 committed Mar 24, 2016
    Configuration menu
    Copy the full SHA
    e95e577 View commit details
    Browse the repository at this point in the history

  2. [discover/tests] update rigid test data

    @spalger
    spalger committed Mar 24, 2016
    Configuration menu
    Copy the full SHA
    5c492e7 View commit details
    Browse the repository at this point in the history

  3. Merge pull request #1 from spalger/pr/6643 

    [discover/tests] update rigid test data
    @colings86
    colings86 committed Mar 24, 2016
    Configuration menu
    Copy the full SHA
    184c0a3 View commit details
    Browse the repository at this point in the history