phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-6055) Improve error reporting for index validation when there are "Not matching index rows"
Date Thu, 30 Jul 2020 22:00:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Geoffrey Jacoby updated PHOENIX-6055:
-------------------------------------
    Comment: was deleted

(was: [~giskender] - Some operators may have legal or contractual restrictions on emitting
production data into their logs, which this would be likely to do. )

> 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)

Mime
View raw message