Document datehistogram with long offsets #93328
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
craigtaverner
added
>docs
|
Documentation preview: |
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
|
Pinging @elastic/es-docs (Team:Docs) |
When offsets are longer than calendar_intervals that are non-standard, like months which differ in length, then the usual rule of all buckets starting at the same day and time will no longer apply. This update attempts to explain this with examples.
These don't seem to be parsable, even though they match the syntax described in the README.asciidoc
craigtaverner
force-pushed
the
datehistogram_long_offsets
branch
from
c9ff4e2
to
fa46605
Compare
abdonpijpelink
approved these changes
Feb 6, 2023
docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
Outdated
Show resolved
Hide resolved
…sciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
…sciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
…sciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
…sciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
craigtaverner
added
auto-backport-and-merge
💚 Backport successful
|
craigtaverner
added a commit
to craigtaverner/elasticsearch
that referenced
this pull request
Feb 6, 2023
* Document datehistogram with long offsets When offsets are longer than calendar_intervals that are non-standard, like months which differ in length, then the usual rule of all buckets starting at the same day and time will no longer apply. This update attempts to explain this with examples. * Removed TEST-skip lines These don't seem to be parsable, even though they match the syntax described in the README.asciidoc * Added // TESTRESPONSE[skip:...] lines * Refined docs description and added more examples * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co> * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co> * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co> * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co> --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Feb 6, 2023
* Document datehistogram with long offsets When offsets are longer than calendar_intervals that are non-standard, like months which differ in length, then the usual rule of all buckets starting at the same day and time will no longer apply. This update attempts to explain this with examples. * Removed TEST-skip lines These don't seem to be parsable, even though they match the syntax described in the README.asciidoc * Added // TESTRESPONSE[skip:...] lines * Refined docs description and added more examples * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc * Update docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When offsets are longer than calendar_intervals that are non-standard, like months which differ in length, then the usual rule of all buckets starting at the same day and time will no longer apply.
This update attempts to explain this with examples.
Fixes: #93180