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
Forward map value extractors to HD indexes #13692
Conversation
This change fixes two issues: 1. The consistency issue: queryable entries returned by HD indexes were unaware of the map value extractors, so it was impossible to extract values provided by the extractors from the returned entries. 2. The performance issue: Extractors.empty is a pretty expensive call and it was performed for every returned entry. According to a slightly modified version of HDIndexPerfTest the throughput is about 2 times higher now. Fixes: https://github.com/hazelcast/hazelcast-enterprise/issues/2109
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.
well done!
Great work Sergey! I'll check it as soon as I have time. You are saving the day here! |
This PRD needs to be backported to 3.10.6. |
@pveentjer 3.10.6 or 3.10.5? |
Two approvals, merging. Thanks for the reviews @jerrinot @vbekiaris ! |
@taburet can you backport to 3.10.x? Thanks! |
Backport is added #13775 |
EE part: https://github.com/hazelcast/hazelcast-enterprise/pull/2227
This change fixes two issues:
The consistency issue: queryable entries returned by HD indexes were
unaware of the map value extractors, so it was impossible to extract
values provided by the extractors from the returned entries.
The performance issue: Extractors.empty is a pretty expensive call
and it was performed for every returned entry. According to a slightly
modified version of HDIndexPerfTest the throughput is about 2 times
higher now.
Fixes: https://github.com/hazelcast/hazelcast-enterprise/issues/2109