phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3757) System mutex table not being created in SYSTEM namespace when namespace mapping is enabled
Date Mon, 03 Apr 2017 17:43:41 GMT

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

Samarth Jain commented on PHOENIX-3757:
---------------------------------------

Yeah, I remember making this change. SYSTEM.MUTEX table doesn't have any corresponding Phoenix
metadata in SYSTEM.CATALOG i.e. it isn't really a phoenix table. We just use this table currently
to control upgrades from running concurrently. So I thought of excluding the table from using
the system name space. Although in hindsight, it would not have mattered? I am curious though
as to what issue are you running into with SYSTEM.MUTEX not being in the SYSTEM namespace?

> System mutex table not being created in SYSTEM namespace when namespace mapping is enabled
> ------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3757
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3757
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>
> Noticed this issue while writing a test for PHOENIX-3756:
> The SYSTEM.MUTEX table is always created in the default namespace, even when {{phoenix.schema.isNamespaceMappingEnabled=true}}.
At a glance, it looks like the logic for the other system tables isn't applied to the mutex
table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message