mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
290c8b8256
The date_histogram accepts an interval which can be either a calendar interval (DST-aware, leap seconds, arbitrary length of months, etc) or fixed interval (strict multiples of SI units). Unfortunately this is inferred by first trying to parse as a calendar interval, then falling back to fixed if that fails. This leads to confusing arrangement where `1d` == calendar, but `2d` == fixed. And if you want a day of fixed time, you have to specify `24h` (e.g. the next smallest unit). This arrangement is very error-prone for users. This PR adds `calendar_interval` and `fixed_interval` parameters to any code that uses intervals (date_histogram, rollup, composite, datafeed, etc). Calendar only accepts calendar intervals, fixed accepts any combination of units (meaning `1d` can be used to specify `24h` in fixed time), and both are mutually exclusive. The old interval behavior is deprecated and will throw a deprecation warning. It is also mutually exclusive with the two new parameters. In the future the old dual-purpose interval will be removed. The change applies to both REST and java clients. |
||
|---|---|---|
| .. | ||
| ccr | ||
| cluster | ||
| dataframe | ||
| document | ||
| graph | ||
| ilm | ||
| indices | ||
| ingest | ||
| licensing | ||
| migration | ||
| miscellaneous | ||
| ml | ||
| rollup | ||
| script | ||
| search | ||
| security | ||
| snapshot | ||
| tasks | ||
| watcher | ||
| aggs-builders.asciidoc | ||
| execution-no-req.asciidoc | ||
| execution.asciidoc | ||
| getting-started.asciidoc | ||
| index.asciidoc | ||
| java-builders.asciidoc | ||
| migration.asciidoc | ||
| query-builders.asciidoc | ||
| supported-apis.asciidoc | ||