-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.4.0 failed to compile and run native script score function #8377
Comments
Same problem here, and I can not find a way (efficient way) to get the score lucene provided within a native score script. |
I think I have the same issue, I wrote my plugin with the instruction in this repo: |
I too suffer from the issue |
In 1.3 and before, there was a weird dual API for setting the score (see #6864). The To access the score from a native script, you should |
@kilnyy, @noamt elasticsearch-native-script-example is updated with a temporary work-around until 1.4.1 is released. |
Cheers! |
Hi y'all,
After upgrading to 1.4.0, I failed to compile my native(Java) score functions which worked well with 1.3.4.
The first issue I ran into is that my function extended
AbstractDoubleSearchScript
and callscore()
to get document score from Lucene, apparently it won't work now with 1.4.0.I wonder if any of you could tell me which method should be called to get the original score of one document. An example of my function looks like:
The second issue is when I just remove the 'score()' method and query ElasticSearch with following parameter:
following error was logged:
I noticed there were some groovy script function changes, but I don't think that should affect the interface of native score function.
Regards,
Andy
The text was updated successfully, but these errors were encountered: