-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Solr textContainsPhrase & Solr Client Tokenizer Alignment #4166
base: master
Are you sure you want to change the base?
Conversation
Closes JanusGraph#4164 Added new test document and updated assertions Use tokenizer that mimics Solr's standardized tokenizer Geo predicate tweaking Implemented TextContainsPhrase for Solr Signed-off-by: Allan Clements <[email protected]>
377dac8
to
cd4bad1
Compare
@VladimirBogomolov Would you like to review? |
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.
Thank you for the fix and the new pushdown rule! I have one question about the tokenizer fix:
In your issue description #4165 you mentioned that you witnessed the bug when migrating from Elasticsearch to Solr. Is it possible to write a test in JanusGraphIndexTest
such that Elasticsearch backend would pass, and Solr backend wouldn't without your fix? I understand you added a new unit test for Solr backend, but it would be even better if we could have a test to ensure the consistent behaviour across index backends.
I believe running the test class I modified without the modified Solr client should demonstrate it. The test class I modified appeared to be executed upon all providers if I'm not mistaken. |
Oh yeah you are right, never mind then! |
Restoring the original client will opt it out of the containsPhrase testing based on the support flags evaluated by the supports method. But I believe it should demonstrate the breakage with regards to the textContains predicate. If not I woefully missed up in my preliminary investigation 😅 |
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.
Oh gosh sorry I completely forgot about this PR. If there's no other review, I'll merge this PR in a week following lazy merge consensus.
Thank you for contributing to JanusGraph!
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
master
)?For code changes:
For documentation related changes:
Fixes #4165
Closes #4164