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

James Taylor commented on PHOENIX-4156:
---------------------------------------

bq. I wanted to disable the scheduled thread so the test can execute the 
rebuild task itself and assert the state of indexes. I don't think we can do 
that by setting the "do not rebuild" index policy on the table.
I see. That seems fine then. Why not a default for the delay of 0?

bq. when the disableIndexOnWriteFailure=false and rebuildIndexOnFailure=false, 
we are relying on the users to replay the mutations, right? So in this case the 
index disable timestamp shouldn't be set?
Correct.

> Fix flapping MutableIndexFailureIT
> ----------------------------------
>
>                 Key: PHOENIX-4156
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4156
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-4156_v1.patch, PHOENIX-4156_v2.patch, 
> PHOENIX-4156_v3.patch, PHOENIX-4156_v4.patch
>
>




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

Reply via email to