[
https://issues.apache.org/jira/browse/PHOENIX-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023209#comment-15023209
]
Enis Soztutar commented on PHOENIX-2431:
----------------------------------------
bq. We've never considered making the deployment of the dependent Tephra jars
optional in maven
I am not concerned about jar dependency, but the deployment change for getting
Phoenix running on top of HBase. Making CATALOG depend on the TM daemon running
means that all deployments should have a TM daemon running in HA mode. Thus
requires rmp changes, deployment, ambari changes, etc.
I am not saying that we should not do it, but more like we should make the
explicit decision to require or not a TM running in all Phoenix deployments
even though you may not have transactional tables.
> Make SYSTEM.CATALOG table transactional
> ---------------------------------------
>
> Key: PHOENIX-2431
> URL: https://issues.apache.org/jira/browse/PHOENIX-2431
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> We currently update the SYSTEM.CATALOG table atomically by using the
> region.mutateRowsWithLocks() call. This works only if the mutations are all
> in the same region which can break down if enough views are created on a base
> table. Instead, now that we have transactions, we should change our
> SYSTEM.CATALOG table to transactional=true and stop using an endpoint
> coprocessor to update the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
