[
https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953905#comment-15953905
]
Josh Elser commented on PHOENIX-3757:
-------------------------------------
bq. I am curious though as to what issue are you running into with SYSTEM.MUTEX
not being in the SYSTEM namespace?
I haven't run into any specific issue, it was just "odd" to me. I expected all
of the "Phoenix SYSTEM" tables to be grouped together in the SYSTEM namespace
(when the namespace mapping was created). I actually couldn't tell you if
clients even have to read/write into that table :)
> 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)
