HPCC-17036 Non interleaved superindexes in a keyed join lost data #9620
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.
A keyedjoin was incorrectly serializing the parts if the superkey
was interleaved, meaning that some key parts were missing from the
slaves and/or the wrong parts might be referenced after the TLK
lookup, resulting in lost matches.
Signed-off-by: Jake Smith jake.smith@lexisnexisrisk.com
Type of change:
Checklist:
Testing:
Specific test with unusual superkey (non-interleaved) was used to verify fix.
Full regression suite was run.