[ https://issues.apache.org/jira/browse/PHOENIX-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-3815: ---------------------------------- Attachment: PHOENIX-3815_v3.patch Rebased patch and made the following changes: - Use ParallelWriterIndexCommitter for transactional tables since we don't need to track disabled tables in that case - Added some more testing around the index that shouldn't be disabled (to make sure it's valid against the data table after write failures to other table. I measured run time of MutableIndexFailureIT with and without the patch and there's not much difference (4:49 vs 5:05). This would be explained with the extra writes to the new index table. Unless there are objects, I'll go ahead and commit this version, [~vincentpoon]. > Only disable indexes on which write failures occurred > ----------------------------------------------------- > > Key: PHOENIX-3815 > URL: https://issues.apache.org/jira/browse/PHOENIX-3815 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > Assignee: Vincent Poon > Fix For: 4.12.0 > > Attachments: PHOENIX-3815.0.98.v2.patch, > PHOENIX-3815.master.v2.patch, PHOENIX-3815.v1.patch, PHOENIX-3815_v3.patch > > > We currently disable all indexes if any of them fail to be written to. We > really only should disable the one in which the write failed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)