[PHOENIX-6055] Improve error reporting for index validation when there are "Not matching index rows"

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.1.0, 4.16.0
• Assignee: Unassigned
• Reporter: Gokcen Iskender
• Created: 30/Jul/20 21:47
• Updated: 29/Jan/21 11:52
• Resolved: 24/Sep/20 22:54

Description

In the IndexRebuildRegionScanner, in the following line we return the timestamp of the latest expected mutation rather than the expected mutation itself.

 

byte[] dataKey = indexMaintainer.buildDataRowKey(new ImmutableBytesWritable(indexRow.getRow()), viewConstants);
String errorMsg = "Not matching index row";
logToIndexToolOutputTable(dataKey, indexRow.getRow(),
getTimestamp(expectedMutationList.get(0)), 0L, errorMsg, isBeforeRebuild,
INVALID_ROW);

 

Instead of expectedMutationList.get(0), expected should be used.

Issue Links

• links to: GitHub Pull Request #891