3 ms·
In a large internal project we still make heavy use of Groovy for scripting. All scripting languages besides the new Painless language were deprecated in versio
by jordanab 9y ago
In a large internal project we still make heavy use of Groovy for scripting. All scripting languages besides the new Painless language were deprecated in version 5, and now in version 6 they are removed. This hampers us in our migration efforts from 5 to 6. Does anyone know if it is still possible to use Groovy through a separate (third party) plugin? I played around a bit with Painless, but can't say that I really like it. Documentation was/is kind of poor, and it seemed to me it somewhat assumed familiarity with Java and it's framework/APIs.
- milesokeefe 9y agoMight be worth trying the Groovy plugin that was needed prior to ES integrating it: https://github.com/elastic/elasticsearch-lang-groovy https://github.com/elastic/elasticsearch-lang-groovy
- jordanab 9y agoThx. I already came across that repo, and seems very outdated. I might have to check out creating my own plugin, and use this as a start.
- laichzeit0 9y agoThey deprecated all scripting langs? Ok this is something new I learned in this thread. That is an extremely lame deprecation. Is ElasticSearch the new Apple? “let’s remove as much functionality as possible for the sake of being as minimal as possible”. Groovy is a fantastic language. It really is a hidden gem. It is my language of choice for cross-platform work, especially in enterprise.
- timv 9y agoGroovy was a security nightmare. The groovy sandbox simply doesn't do enough to protect a server. Our scripting language "Painless" is faster and more secure than we could achieve with groovy, so in Elasticsearch 5.0 we made Painless the default and deprecated groovy. In 6.0, groovy is gone. We didn't do it to be minimalist, but we couldn't in good conscience continue to ship an insecure scripting language when we had an alternative. Disclosure: I work at Elastic on security.