-
Notifications
You must be signed in to change notification settings - Fork 369
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
update for ES7.0.0 #219
update for ES7.0.0 #219
Conversation
Updated to use Elasticsearch 7.0.0
|
Fixed the remaining tests
@nomoa @softwaredoug @worleydl I think this PR should be ready for review now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great!
left some comments (mostly minor).
As for the situation about the new restriction of having positive scores I'd be for the following solution while we fix rankers:
Add new param to the ltr/sltr query that would indicate the failure mode in case of negative score returned by some rankers:
- fail (throw IOException() from the score method)
- log a warning and clamp min to 0
I'd be for opening a dedicated ticket to discuss this.
src/main/java/com/o19s/es/ltr/action/TransportAddFeatureToSetAction.java
Outdated
Show resolved
Hide resolved
src/main/java/com/o19s/es/ltr/query/DerivedExpressionQuery.java
Outdated
Show resolved
Hide resolved
@@ -148,22 +146,19 @@ public void testLogging() throws IOException { | |||
} | |||
} | |||
|
|||
public void testBogusQuery() throws IOException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should keep this test perhaps just expect that IllegalArgumentException is thrown?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue is we cant even build a BoostQuery
object anymore since that is the one that throws IllegalArgumentException
so essentially we never even get to the code we want to test.
and the circleci config will have to be updated to pull java 12 I suppose. |
Curious about the status of the PR. I have used the plugin with my basic sample, everything still seems to work. |
@jettro I need to address the comments mentioned by @nomoa. Should get to them sometime later this week. Been somewhat busy with https://haystackconf.com/2019/evolution/. |
I dont see openjdk-12 image available on circleci. https://circleci.com/docs/2.0/circleci-images/#openjdk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Still some work to be done to get it completely working:
Scorer
must now implementgetMaxScore
. This is the upstream lucene PR. For now I return a default value for all Scorer implementations, not sure how this method affects some of the custom Scorers.