[
https://issues.apache.org/jira/browse/PHOENIX-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090137#comment-16090137
]
Samarth Jain commented on PHOENIX-4028:
---------------------------------------
Thanks for the updated patch and tests, [~jamestaylor].
It would be good to have a few more test cases covering these conditions:
{code}
{ false, false, true, true, true, true, null} - test that failure of rebuild
task works correctly when namespace mapping is enabled
{ false, false, false, true, true, true, false} - test that failure of rebuild
task works correctly when index write failure exception is not thrown back to
the client with namespace mapping disabled
{ false, false, false, true, true, true, false} - test that failure of rebuild
works correctly when index write failure exception is not thrown back to the
client with namespace mapping enabled
{code}
> 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_v2.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)
