phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4028) Provide option to not throw index write failure back to client
Date Sat, 15 Jul 2017 04:32:00 GMT

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

James Taylor updated PHOENIX-4028:
----------------------------------
    Attachment: PHOENIX-4028.patch

Please review, [~samarthjain]. I also changed your rebuild test to a parameter in MutableIndexFailureIT.
That way, you can run it only for the combinations you want to test it for rather than cause
all tests to run twice.

> Provide option to not throw index write failure back to client
> --------------------------------------------------------------
>
>                 Key: PHOENIX-4028
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4028
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4028.patch, PHOENIX-4028_wip.patch
>
>
> Much like our DISABLE_INDEX_ON_WRITE_FAILURE and REBUILD_INDEX_ON_WRITE_FAILURE table
properties, we need a THROW_INDEX_WRITE_FAILURE boolean option that can be used to prevent
the index write from being thrown back to the client. In this case, the index failure policy
would still be executed (i.e. disabling the index on a write failure), but any retry logic
for the client would be avoided. The index would be eventually consistent based on the background
partial index rebuild thread.



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

Mime
View raw message