-
Notifications
You must be signed in to change notification settings - Fork 183
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
[BUG] 0.2.1 branch breaks completion suggesters #107
Comments
The bug is in union deserializer. It removes all fields as you add members, for example two members have The field removal can happen in the |
Fix might be: remove all of the field removal from
then at top of
And you end up with correct unique fields. |
Verified this code change solves the problem for the use case that started this bug. |
@apatrida Care to PR a fix? |
@iamdanhart I think the best place to start is trying to write a failing unit test in this project for this problem. I would check out the code and build it first (https://github.com/opensearch-project/opensearch-java/blob/main/DEVELOPER_GUIDE.md has lots of helpful things), then try to implement a failing test? |
@dblock Here's the failing test and stacktrace. I added this to AbstractRequestIT and ran RequestIT. Is posting it here sufficient or should I make a PR?
|
Make a PR! If you have time try to fix it. We’ll help you. |
@dblock Thank you for your guidance in this process! So that I can set expectations for my stakeholders when they have questions about my integrating with OpenSearch, is there a rough estimate for when the next release would get cut? |
The java client has recently implemented a faster release process, and a release went out this week. If you have an urgent need for your fix to get into maven, make a request in a separate issue. I don't see why it would take more than a week or two to get a release out after your PR gets merged, and it could be under a week if it's been a while and there are other merged PRs waiting to get out. |
Thanks for that explanation. That sounds like a reasonable time frame. |
This will be released in v2.3.0 (#380). |
What is the bug?
The required fields for completion suggesters are incorrect. Some fields with default values are marked as required fields. In completion suggester, this includes
transpositions
andunicodeAware
and therefore breaks code that doesn't set these.Also, the response objects for completion suggestion do not work. Completion suggestion results are coming back as
isTerm
and therefore blowing up since they do not havescore
or some other values in the correct places, and all of their other fields are therefore missing.@imRishN
The text was updated successfully, but these errors were encountered: