Red Hat Bugzilla – Bug 1251371
Elasticsearch versions 1.4.0+ are packaged without groovy support but groovy is default scripting language
Last modified: 2016-07-19 15:16:27 EDT
When Elasticsearch version was incremented beyond 1.4.0 a new dependency was created against groovy-all-2.4.x.jar which should be installed in /usr/share/elasticsearch/lib
Without this library installed, Elasticsearch will fail all queries that use scripting as groovy is now set as the default scripting language from 1.4.0 onward.
without this support Elastic-search fails on a query with the exception
"script_lang not supported [groovy]]"
Installing Elastic-search downloaded from Elastic-search site correctly installs the groovy support and queries do not fail.
Hello. I'm using packed elastic as it is. if you are missing something, I will be happy to include your patch or make you comaintainer and you can fix it.
Otherwise it is going to be closed-cantfix because I can not spent more free time on it. sorry.
I will check it out and see if i can create a package that fixes this, elasticsearch themselves maintain .rpm versions that work perfectly, and include goodies like systemd units, perhaps it would be better to just import thier packages.
(In reply to Tim Hawkins from comment #2)
> I will check it out and see if i can create a package that fixes this,
> elasticsearch themselves maintain .rpm versions that work perfectly, and
> include goodies like systemd units, perhaps it would be better to just
> import thier packages.
Its not posible. Theirs packages are full of embedded stuff.
Of how much, yo may see the original review.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.