You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:22:14 UTC

[jira] [Resolved] (PHOENIX-573) Making index writing pluggable.

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

Gabriel Reid resolved PHOENIX-573.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Making index writing pluggable.
> -------------------------------
>
>                 Key: PHOENIX-573
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-573
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Jason Yates
>
> There are two main pluggability points: (1) writing the index and (2) handling failure.
> This provides the option to mix and match choices. For instance, it would be pretty easy to
> write an AsyncHBase writer and use the standad KillServerOnFailurePolicy to ensure that
> the server fails if all index writes don't succeed.
> By default, we retain the existing behavior, which uses a thread-pool to write to a cache of HTables and kills the server if any write fails.



--
This message was sent by Atlassian JIRA
(v6.2#6252)