dev/core#2820: Deduping produces bad results after a rule change #21509
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
When a dedupe rule is changed, the results appear to be cached.
Reproduction steps
Before
Shows previous results - those with first or last matching names. Click the 'Threshold' box and note scores of 5 - below the specified threshold of 10.
After
Should only list contacts with matching first and last names where threshold score is 10.
Technical Details
Regression is caused by 9d2f6d5#diff-fe60c89ebe94bbd40114d135459371cc53708db1f2952ade6c0ce9b3468c4dabR2038 this change and affecting since 5.3.0
Fixed by correcting the cache key which is used to fetch and delete the cache of previous dedupe rule.
Comments
ping @eileenmcnaughton @aydun