# Date\_histogram: Unknown time-zone ID: Europe/Kyiv

**URL:** <https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188>\
**Category:** Elasticsearch\
**Created:** [December 12, 2023, 6:42pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188 "2023-12-12T18:42:44Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Inbal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inbal/32/129817_2.png) [@Inbal](https://discuss.elastic.co/u/Inbal)\
**Post date:** [December 12, 2023, 6:42pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/1 "2023-12-12T18:42:44Z")

</div>

Hey, I have a es search with aggregations which contains date\_histogram with time\_zone parameter. When I'm choosing "Europe/Kyiv" as time\_zone  
I'm getting the following error reason: "Unknown time-zone ID: Europe/Kyiv".  
Any idea why it happens?

Edit: Im using V8.1.3

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 12, 2023, 7:19pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/2 "2023-12-12T19:19:32Z")

</div>

Which version are you using?

---

<div class="post-metadata">

**Author:** ![Inbal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inbal/32/129817_2.png) [@Inbal](https://discuss.elastic.co/u/Inbal)\
**Post date:** [December 12, 2023, 7:31pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/3 "2023-12-12T19:31:11Z")

</div>

Using 8.1.3

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 12, 2023, 7:40pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/4 "2023-12-12T19:40:29Z")

</div>

> [@Inbal](#):
>
> Using 8.1.3

8. **1**.3 or 8. **11**.3?

---

<div class="post-metadata">

**Author:** ![Inbal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inbal/32/129817_2.png) [@Inbal](https://discuss.elastic.co/u/Inbal)\
**Post date:** [December 12, 2023, 7:50pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/5 "2023-12-12T19:50:07Z")

</div>

8. **1**.3 🙂

---

<div class="post-metadata">

**Author:** ![Inbal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inbal/32/129817_2.png) [@Inbal](https://discuss.elastic.co/u/Inbal)\
**Post date:** [December 12, 2023, 7:57pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/6 "2023-12-12T19:57:27Z")

</div>

@leandrojmp I found this issue [[CI] JdbcFrozenCsvSpecIT 'Unknown time-zone ID' failures · Issue #95044 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/95044#issuecomment-1637950541)  
might be relatd 🤔

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 12, 2023, 7:59pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/7 "2023-12-12T19:59:01Z")

</div>

> [@Inbal](#):
>
> 8. **1**.3

Yeah, I think that's the issue then.

8.1.3 is from April 2022 according to this [blog post](https://www.elastic.co/blog/elastic-stack-8-1-3-released).

_Europe/Kiev_ was renamed to _Europe/Kyiv_ in August 2022, on the 2022b release of tz data according to [this](https://mm.icann.org/pipermail/tz-announce/2022-August/000071.html).

And [according to this](https://www.oracle.com/java/technologies/tzdata-versions.html) it was included on java versions from August 2022.

But I'm not sure if just upgrading to a newer version or using a newer java will solve the issue.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 12, 2023, 8:00pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/8 "2023-12-12T20:00:40Z")

</div>

> [@Inbal](#):
>
> might be relatd

This is issue seems to be related to the CI elastic uses, not sure it would apply to your case.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 12, 2023, 8:01pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/9 "2023-12-12T20:01:40Z")

</div>

Can you share your aggregation? Or at least the date\_histogram part.

---

<div class="post-metadata">

**Author:** ![Inbal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inbal/32/129817_2.png) [@Inbal](https://discuss.elastic.co/u/Inbal)\
**Post date:** [December 12, 2023, 8:15pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/10 "2023-12-12T20:15:57Z")

</div>

Sure,

```auto
      "date_histogram": {
        "field": "timestamp",
        "calendar_interval": "day",
        "time_zone": "Europe/Kyiv"
      },

```

I checked `Europe/Kiev` and it works.  
Ill try to upgrade, appreciate your help!!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 9, 2024, 8:16pm UTC](https://discuss.elastic.co/t/date-histogram-unknown-time-zone-id-europe-kyiv/349188/11 "2024-01-09T20:16:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
