[
https://issues.apache.org/jira/browse/PHOENIX-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200573#comment-17200573
]
Istvan Toth commented on PHOENIX-6055:
--------------------------------------
As part of checking the new PreCommit job, I've checked why this does not
apply.
It seems that this patch was already part of the 5.x indexing rebase in
PHOENIX-6067 , and is already in 4.x as well.
> Improve error reporting for index validation when there are "Not matching
> index rows"
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-6055
> URL: https://issues.apache.org/jira/browse/PHOENIX-6055
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Gokcen Iskender
> Priority: Major
> Attachments: PHOENIX-6055.master.001.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
