Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BarChart: Failed to parse date field #76820

Closed
lorehek opened this issue Sep 4, 2020 · 5 comments
Closed

BarChart: Failed to parse date field #76820

lorehek opened this issue Sep 4, 2020 · 5 comments
Labels
Feature:Search Querying infrastructure in Kibana impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort

Comments

@lorehek
Copy link

lorehek commented Sep 4, 2020

Kibana version: v 7.6.2

Elasticsearch version: v 7.6.2

Server OS version:
Linux ubuntufj01-ngan 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Browser version:
Google Chrome Version 85.0.4183.83

Browser OS version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:
Error seen:
Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"parse_exception","reason":"failed to parse date field [1598029183000] with format [yyyy-MM-dd HH:mm:ssZZ]: [failed to parse date field [1598029183000] with format [yyyy-MM-dd
Steps to reproduce:
Steps to reproduce

  1. Create and index and add a few records
    PUT /error_test_index
    {
    "mappings": {
    "properties": {
    "time" : {
    "type" : "date",
    "format" : "yyyy-MM-dd HH:mm:ssZZ"
    }
    }
    }
    }

PUT /error_test_index/_doc/3
{
"time":"2020-08-21 12:59:43-0400"
}

PUT /error_test_index/_doc/2
{
"time":"2020-08-21 11:59:43-0400"
}

PUT /error_test_index/_doc/1
{
"time":"2020-08-21 10:59:43-0400"
}

  1. Create a vertical bar visualization and split the series on Aggregation -> terms and field->time.
    For the time range, a 3-level stacked bar should be displayed.

  2. Select one bar and the error should appear: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"parse_exception","reason":"failed to parse date field [1598029183000] with format [yyyy-MM-dd HH:mm:ssZZ]: [failed to parse date field [1598029183000] with format [yyyy-MM-dd HH:mm:ssZZ]]"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":

  3. DSL Query is
    {
    "query": {
    "match_phrase": {
    "time": 1598029183000
    }
    }
    }

Expected behavior:
GitBeforeClickOnPurple
GitClickedOnPurple
GitDiscoveryRecordsShown
GitEditFilter
GitStackedBarChart

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:
5. A modification to the query allows for success
{
"query": {
"match_phrase": {
"time": "2020-08-21 10:59:43-0400"
}
}
}

@monfera monfera added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Sep 7, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@timroes timroes added Feature:Search Querying infrastructure in Kibana Team:AppArch and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Sep 7, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@timroes
Copy link
Contributor

timroes commented Sep 7, 2020

This seems to be an error that we create timestamp filters in scenarios where the mapping has an explicit format set, and thus will deny timestamp filters.

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Jun 2, 2021
@lukasolson
Copy link
Member

This appears to be resolved.

@Sagesh
Copy link

Sagesh commented Jun 29, 2022

@lukasolson, In which release did the issue got resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Search Querying infrastructure in Kibana impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort
Projects
None yet
Development

No branches or pull requests

6 participants