-
Notifications
You must be signed in to change notification settings - Fork 3.3k
fix(test): resolve search test flakiness with enhanced SearchRequestHandler cache key #15299
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
base: master
Are you sure you want to change the base?
fix(test): resolve search test flakiness with enhanced SearchRequestHandler cache key #15299
Conversation
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
|
||
| @Override | ||
| public int hashCode() { | ||
| return entitySpecs.hashCode(); |
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.
implementation of hashcode and equals is out of sync. It can reimplemented
| "urn:li:dataset:(urn:li:dataPlatform:bigquery,bigquery-public-data.covid19_geotab_mobility_impact.ca_border_wait_times,PROD)"); | ||
| assertTrue(explainResponse.isExists()); | ||
| assertEquals(explainResponse.getExplanation().getValue(), 18.0f); | ||
| assertEquals(explainResponse.getExplanation().getValue(), 1.25f); |
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.
why this has changed ? Seems to be unrelated with the fix
Replaced entitySpecs-based cache key with comprehensive SearchHandlerKey that includes all configuration components. This prevents test instability where different search configurations with identical entitySpecs would incorrectly share already cached handler instances.