Index pattern always treats field named "_timestamp" as a date regardless of mapping #121710
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Data Views
Data Views code and UI - index patterns before 8.0
impact:needs-assessment
Product and/or Engineering needs to evaluate the impact of the change.
loe:small
Small Level of Effort
Kibana version:
7.16.1
Elasticsearch version:
7.16.1
Server OS version:
ESS
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
When creating an index pattern, if you have a field named
_timestamp
it will always be listed as an option for the time field for the index pattern, even if this field is already mapped as a non date type. Treating this field as a date causes issues in Discover, which fails to load index patterns that have this field due to date formatting being applied to a non-date data type, such as :Steps to reproduce:
_timestamp
field:_timestamp
field has a numeric mapping withGET /timestamp_test/_mapping
timestamp_test
index, set@timestamp
as the time field. Note that_timestamp
was an option for the time field_timestamp
is correctly shown as a numeric field type_timestamp
doesn't support formatsExpected behavior:
If
_timestamp
isn't mapped as a date, we shouldn't try to to date things to it.Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: