phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2431) Make SYSTEM.CATALOG table transactional
Date Fri, 20 Nov 2015 23:03:10 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019006#comment-15019006
] 

Enis Soztutar commented on PHOENIX-2431:
----------------------------------------

Maybe this is a higher level question, but do we want to make transactions support fully optional
or not. Meaning that when trx lands in master, can deployments be still able to work without
having to deploy tephra or omid or not? 

If we want to keep the current deployment model, this jira should also be optional, no? 

> 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)

Mime
View raw message