[GH-ISSUE #271] Upgrading ES to 6.8? #258

New issue

Closed

opened 2026-02-27 15:55:51 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:55:51 +03:00

Owner

Originally created by @dareneiri on GitHub (Nov 28, 2019).
Original GitHub issue: https://github.com/RD17/ambar/issues/271

I was wondering if there was any plan for Ambar to upgrade to ES 6.8+?
In 6.8, some of the security features that used to require licensing became free.
https://www.elastic.co/guide/en/elasticsearch/reference/6.8/release-notes-6.8.0.html

I'm aware this would require quite a bit of effort in resolving the mappings, especially since ES 6.0 removes mapping types.

I know in a previous issue where this was raised, one of the factors was that the morphology plugin is only available for 5.6. However there are forks available that support ES 6.6+
https://github.com/xumix/elasticsearch-analysis-morphology
https://github.com/nkoshell/elasticsearch-analysis-morphology

Originally created by @dareneiri on GitHub (Nov 28, 2019). Original GitHub issue: https://github.com/RD17/ambar/issues/271 I was wondering if there was any plan for Ambar to upgrade to ES 6.8+? In 6.8, some of the security features that used to require licensing became free. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/release-notes-6.8.0.html I'm aware this would require quite a bit of effort in resolving the mappings, especially since ES 6.0 removes mapping types. I know in a previous issue where this was raised, one of the factors was that the morphology plugin is only available for 5.6. However there are forks available that support ES 6.6+ https://github.com/xumix/elasticsearch-analysis-morphology https://github.com/nkoshell/elasticsearch-analysis-morphology

kerem

2026-02-27 15:55:51 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-27 15:55:51 +03:00

Author

Owner

@stale[bot] commented on GitHub (Dec 13, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 13, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.