[
https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180105#comment-16180105
]
Josh Elser commented on PHOENIX-3757:
-------------------------------------
[~karanmehta93], go for it!
I honestly don't remember - I'd have to refresh myself, it's been so long.
I recall Samarth had asked to try to change the IT's base class. I was worried
not using a fresh HBase cluster would result in us not actually testing what we
think we're testing (if the system tables exists or the PhoenixDriver has any
cached info). This requires some insight.
I think Ankit had some edge cases which I wasn't correctly handling -- JIRA
will serve as a better record than my memory for sure.
> 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
> Labels: namespaces
> Fix For: 4.12.0
>
> Attachments: PHOENIX-3757.001.patch, PHOENIX-3757.002.patch
>
>
> 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.4.14#64029)
