You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gokcen Iskender (Jira)" <ji...@apache.org> on 2020/07/30 21:50:00 UTC
[jira] [Updated] (PHOENIX-6055) Improve error reporting for index
validation when there are "Not matching index rows"
[ https://issues.apache.org/jira/browse/PHOENIX-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gokcen Iskender updated PHOENIX-6055:
-------------------------------------
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.
> 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
>
> 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)