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

Hadoop QA commented on PHOENIX-4178:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12888635/PHOENIX-4178_v2.patch
  against master branch at commit 944bed73585a5ff826997895c2da43720b229d8a.
  ATTACHMENT ID: 12888635

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 7 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1474//console

This message is automatically generated.

> Detect failed index write while rebuilder is running with index staying active
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4178
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4178
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4178.patch, PHOENIX-4178_v2.patch
>
>
> If an index write fails while the rebuilder is running, we need to make sure 
> to run the rebuilder again so we don't need miss any rows. This can only 
> happen when the index is left active, as otherwise the index will transition 
> back to disabled and we'll end up rerunning the rebuilder.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to