ElasticSearchIllegalArgumentException[failed to execute script];

ElasticSearchIllegalArgumentException[failed to execute script]; nested: ScriptException[dynamic scripting disabled];

Sviatlana Varabyova

Vote:

Hi!

We found that the developers indexes were cleared yesterday.

We created new indexes and the appropriate ps scripts were run to check dynamic mappings.

But during the indexing the errors appeared:

2015-02-25 09:36:19,927 [13] ERROR Customer.Commerce.Business.Search.FindProvider.FindSearchProvider: Indexing error:

ElasticSearchIllegalArgumentException[failed to execute script]; nested: ScriptException[dynamic scripting disabled];

How could we fix the issue with developer indexes?

#117962

Feb 25, 2015 10:53

Pavel Nezhencev

Vote:

We are using "Random2Find" lib, that uses script-based sorting. Find started returning "400 Bad Request" in development environments recently. We have a similar error: "ScriptException[dynamic scripting disabled]". Didn't fix it yet :(

And yes, production indexes work fine.

#117994

Edited, Feb 25, 2015 15:12

Sviatlana Varabyova

Vote:

Hi!

Thank you for reply.

What version of elasticsearch is used for developer indexes?

#118018

Edited, Feb 26, 2015 6:31

Pavel Nezhencev

Vote:

I don't know. I wrote a request to EPiServer support regarding this problem and waiting for their help.

#118031

Feb 26, 2015 11:12

Andrew Sanin

Vote:

As I found out from EPiServer, in EPiServer.Find 9 custom scripting is disabled, so you will need to find another way how to solve your tasks.

I assume this was done for security reasons.

#118327

Mar 04, 2015 14:26

Pavel Nezhencev

Vote:

"Random2Find" lib was updated a week ago and it uses native "randomvaluegenerator" instead of custom scripting, so it works fine with Find 9. This update fixed our issue.

#118580

Mar 10, 2015 12:54

Sviatlana Varabyova

Vote:

Thank you!

#118747

Mar 13, 2015 7:16