[ 
https://issues.apache.org/jira/browse/PHOENIX-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200416#comment-17200416
 ] 

Hadoop QA commented on PHOENIX-6055:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} PHOENIX-6055 does not apply to master. Rebase required? Wrong 
Branch? See 
https://yetus.apache.org/documentation/in-progress/precommit-patchnames for 
help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | PHOENIX-6055 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/13011978/PHOENIX-6055.master.001.patch
 |
| Console output | 
https://ci-hadoop.apache.org/job/PreCommit-PHOENIX-Build/35/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |


This message was automatically generated.



> 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: 20m
>  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)

Reply via email to