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

Date histogram interval: ElasticSearchParseException #609

Closed
ineu opened this issue Oct 25, 2013 · 2 comments
Closed

Date histogram interval: ElasticSearchParseException #609

ineu opened this issue Oct 25, 2013 · 2 comments

Comments

@ineu
Copy link

ineu commented Oct 25, 2013

Hello.
With ES 0.90.5 date histograms are partially working: if you select '1M' or 'auto', you get 400 from ES and "ElasticSearchParseException[Failed to parse [auto]]" in kibana. According to ES docs (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-date-histogram-facet.html):

The interval allows to set the interval at which buckets will be created for each hit. It allows for the constant values of year, quarter, month, week, day, hour, minute.
It also support time setting like 1.5h (up to w for weeks).

So neither '1M' nor 'auto' are valid values.

rashidkpc pushed a commit to rashidkpc/kibana that referenced this issue Oct 25, 2013
@KallDrexx
Copy link

Why was month removed instead of replaced with the correct interval value (since the ES docs claim that it supports month intervals)?

@serboctor
Copy link

Sending 'month' instead of '1M' to elasticsearch works fine. But currently Kibana doesn't accept 'month', so if you update the code to accept 'month' then everything will work fine.

w33ble pushed a commit to w33ble/kibana that referenced this issue Sep 13, 2018
* Added EUI to series style. Removed unnecessary CSS and class names

* Cleaned up spacing in simple template for series style

* Fixed uncontrolled select warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@ineu @KallDrexx @rashidkpc @serboctor and others