Update description of mandatory timestamp field #94983
Open
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
|
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
|
Documentation preview: |
elasticsearchmachine
added
v8.7.1
needs:triage
pxsalehi
added
:Analytics/EQL
elasticsearchmachine
added
the
Team:QL (Deprecated)
|
Pinging @elastic/es-ql (Team:QL) |
wchaparro
added
the
Team:Analytics
elasticsearchmachine
removed
the
Team:QL (Deprecated)
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
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.
While experimenting with EQL I noticed it raised this error when the timestamp field was mapped as
datewith formatyyyy-MM-dd HH:mm:ss:search_phase_execution_exception: [parse_exception] Reason: failed to parse date field [1680434649000] with format [yyyy-MM-dd HH:mm:ss]In particular, it happens when making a sequence query: https://www.elastic.co/guide/en/elasticsearch/reference/8.7/eql-syntax.html#eql-sequences
This gets solved when formatting the timestamp field as
epoch_millis.I'm not sure whether this is expected and fixing the docstring is enough or a bigfix ticket is needed.