[
https://issues.apache.org/jira/browse/PHOENIX-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014219#comment-15014219
]
Eli Levine commented on PHOENIX-2431:
-------------------------------------
There is code that allows add/drop columns on tables with views as long as
parent table and view metadata are in the same region. After SYSTEM.CATALOG is
transactional we can probably remove that logic and always allow metadata
mutations for tables with views.
> 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)
