# After upgrade from ES-2.1.1 to ES-2.2.0 groovy scripting is broken **URL:** \ **Category:** Elasticsearch\ **Created:** [February 4, 2016, 4:28pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-2-1-1-to-es-2-2-0-groovy-scripting-is-broken/40977 "2016-02-04T16:28:36Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![David\_Baird](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@David\_Baird](https://discuss.elastic.co/u/David_Baird)\ **Post date:** [February 12, 2016, 12:23pm UTC](https://discuss.elastic.co/t/after-upgrade-from-es-2-1-1-to-es-2-2-0-groovy-scripting-is-broken/40977/13 "2016-02-12T12:23:53Z")
+1 on this one. I'm running embedded in a grails app, so groovy is already on the classpath. I get a (non-fatal) stack trace when I create the node: script\_lang not supported [groovy] when it encounters my .groovy file in the script dir. It used to work just fine on 1.7.x. I tried adding an inline script field using the search builder, but it fails in a similar way, claiming "script\_lang not supported [groovy]". Any help would be greatly appreciated. \*\*\* Update: I think the reason why it doesn't work is because groovy as a scripting language has been pulled out into the 'lang-groovy' plugin (see [https://github.com/elastic/elasticsearch/pull/13834](https://github.com/elastic/elasticsearch/pull/13834)). This is a problem for embedded nodes because there doesn't seem to be a way to install plugins using the NodeBuilder (see [Add plugins from classpath in embedded Elasticsearch client node](https://discuss.elastic.co/t/add-plugins-from-classpath-in-embedded-elasticsearch-client-node/36269)). I think in the short term 2.1.2 still works as it did before, so I'll be rolling back to that version for now. --- _[View the full topic](https://discuss.elastic.co/t/after-upgrade-from-es-2-1-1-to-es-2-2-0-groovy-scripting-is-broken/40977)._