Summary

Adds the dateHistogramInterval utility, which can be used to calculate the correct interval key (calendar_interval or fixed_interval) for a given interval string (like 10s, 1h, etc.).

The return will be an object that can simply spreaded into a date_histogram body. So you should replace your previous interval key by a call to that function:

// You can also use an relative import to the path `src/legacy/core_plugins/data/common` instead
+ import { dateHistogramInterval } from 'plugins/data/common';

const aggregation = {
  date_histogram: {
    field: '@timestamp',
-   interval: '10s',
+   ...dateHistogramInterval('10s'),
  },
};

This function will throw an error if the interval itself is not a valid Elasticsearch interval (like 2w, 5.0h, ...). Please make sure if you use it for user input, that the user input is properly validated beforehand and you show the user a meaningful error message. You can use the isValidEsInterval function as follows:

import { isValidEsInterval } from 'plugins/data/common';

const isValid: boolean = isValidEsInterval('10s');

Release Summary: Migrate date_histograms to the new calendar_interval/fixed_interval. Solves some deprecation warnings in Kibana.

For reviewers

This PR adds a bit of tech-debt, since we import directly from the plugins/data/common folder (which is not one of the root folders we should import later on). Unfortunately there are still a couple of unsolved issues around testing and NP plugins, why we decided to for now introduce that tech-debt, especially since it's really easy to change those imports later on.

This PR also makes use of this method in courier via AggConfig and also makes sure the editor properly validates that value beforehand.

There are a lot of test fixes, now that the AggConfig actually needs a valid interval since it would otherwise throw an exception.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• [ ] This was checked for cross-browser compatibility, including a check against IE11
• [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

• [ ] This was checked for breaking API changes and was labeled appropriately
• [ ] This includes a feature addition or change that requires a release note and was labeled appropriately