You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2017/10/11 22:37:00 UTC
[jira] [Updated] (PHOENIX-4028) Provide option to not throw index
write failure back to client
[ https://issues.apache.org/jira/browse/PHOENIX-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-4028:
----------------------------------
Labels: secondary_index (was: )
> 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
> Labels: secondary_index
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4028.patch, PHOENIX-4028_addendum1.patch, PHOENIX-4028_v2.patch, PHOENIX-4028_v3.patch, PHOENIX-4028_v4.patch, PHOENIX-4028_v5_wip.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)