[
https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982342#comment-15982342
]
Lars Hofhansl commented on PHOENIX-3811:
----------------------------------------
I think this should be configurable per index or at least per table.
Many use cases may want this behavior, but I suspect there most do not want
incorrect answers.
At least per table should not be hard with HBase's per table config overrides.
> Ignore index write failure and let client deal with failure
> -----------------------------------------------------------
>
> Key: PHOENIX-3811
> URL: https://issues.apache.org/jira/browse/PHOENIX-3811
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> We should provide a way to configure the system so that the server takes no
> specific action when an index write fails. Since we always throw the write
> failure back to the client, the client can often deal with failures more
> easily than the server since they have the batch of mutations in memory.
> Often times, allowing access to an index that may be one batch behind the
> data table is better than disabling it given the negative performance that
> will occur while the index cannot be written to.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
