[
https://issues.apache.org/jira/browse/PHOENIX-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495603#comment-16495603
]
James Taylor commented on PHOENIX-4752:
---------------------------------------
I don't see a benefit or need here. Phoenix treats it's SYSTEM.CATALOG as the
source of truth and updates to it are atomic. HBase metadata changes are
performed before the update of SYSTEM.CATALOG. Index builds that fail do not
put the index into an active state.
IMHO, I think the work identified in this document is higher priority:
https://docs.google.com/document/d/16BWU73qlnCQdxCflM3LScyIxE_OGi76ZYT2WHUfewiE
> Phoenix with Procedure v2
> -------------------------
>
> Key: PHOENIX-4752
> URL: https://issues.apache.org/jira/browse/PHOENIX-4752
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Karan Mehta
> Priority: Major
>
> [Procedure Framework
> (Pv2)|https://docs.google.com/document/d/1QLXlVERKt5EMbx_EL3Y2u0j64FN-_TrVoM5WWxIXh6o/edit#heading=h.df9krsl9k16]
> framework in HBase (available from HBase 1.1 and up) allows users to build
> multi step procedures with built in fault tolerance. The framework was
> originally inspired from Fault tolerant executor (FATE) framework from Apache
> Accumulo. This is essentially achieved by declaring the procedure as a series
> of idempotent execution functions and providing persistence for the result of
> each execution. In case of failures, the new owner can first determine the
> in-flight procedures and take on its execution. The framework also allows to
> build a tree (DAG) of procedures i.e. a procedure can have one or more child
> procedures. The next step of procedure will only be executed once all its
> child process have successfully completed execution. This can be leveraged by
> Apache Phoenix for several of its functions.
> I created a doc [Phoenix with
> Procedurev2|https://docs.google.com/document/d/1vmaK7Yz7TTbzuBHPR09d4LqtfAj6tkPT0-DjS6nQ6QA/edit]
> to consolidate some of the use cases. Please provide comments / ideas to
> improve upon it. Also comment on the feasibility vs usefulness of doing it.
> [~elserj] [~giacomotaylor] [~mbertozzi]
> FYI [~apurtell] [~tdsilva]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
