# Backport of a Lucene bugfix (Lucene 9.0/ES 8.0)?

**URL:** <https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093>\
**Category:** Elasticsearch\
**Created:** [June 24, 2022, 9:20am UTC](https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093 "2022-06-24T09:20:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhugo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhugo/32/99205_2.png) [@mhugo](https://discuss.elastic.co/u/mhugo)\
**Post date:** [June 24, 2022, 9:20am UTC](https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093/1 "2022-06-24T09:20:45Z")

</div>

Hi,  
We are migrating from ES 6.8 to ES 7.17 and encountered a bug during indexing for some complex shapes. It turns out the issue is a tessellation bug in Lucene that has been fixed in Lucene 9.0 (see [[LUCENE-9580] Tessellator failure for a certain polygon - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-9580))

Since we cannot migrate to ES 8.0 yet (that requires a full reindexing that cannot be done yet), I would like to have the Lucene bugfix backported into a future ES 7.17.x release.  
What is the path to follow ? I can submit a PR to Lucene so that a next 8.11.y release of Lucene (the branch used on ES 7.17) includes this patch. Is there a chance this potential new Lucene release will be intergrated into a future ES 7.17.x release ?

Thanks !

---

<div class="post-metadata">

**Author:** ![Ignacio\_Vera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ignacio_vera/32/36674_2.png) [@Ignacio\_Vera](https://discuss.elastic.co/u/Ignacio_Vera)\
**Post date:** [June 24, 2022, 10:56am UTC](https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093/2 "2022-06-24T10:56:39Z")

</div>

Hi @mhugo,

It would be grate if you open a PR in Lucene. I cannot assure you that the change will be integrated in Elasticsearch but adding it in Lucene 8.11 will be the first step. I think it will be worthy to open an issue in the Elasticsearch repository as well so we can discuss possible options.

Aplogies for the hassle.

---

<div class="post-metadata">

**Author:** ![mhugo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhugo/32/99205_2.png) [@mhugo](https://discuss.elastic.co/u/mhugo)\
**Post date:** [June 24, 2022, 1:23pm UTC](https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093/3 "2022-06-24T13:23:37Z")

</div>

Thanks for your answer. I'll submit a PR on Lucene and open an issue on Elasticsearch then.

---

<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:** [July 22, 2022, 1:23pm UTC](https://discuss.elastic.co/t/backport-of-a-lucene-bugfix-lucene-9-0-es-8-0/308093/4 "2022-07-22T13:23:54Z")

</div>

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