[
https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957511#comment-15957511
]
Josh Elser commented on PHOENIX-3757:
-------------------------------------
bq. For your new test class, you would probably want to extend
BaseUniqueNamesOwnClusterIT. Are you testing for the case where the system
tables are also using name spaces? I didn't see the property
It is -- that's actually coming in from the changes in PHOENIX-3756. At this
point, it might be better for me to wait for that one to land (so it's clear
what is being changed here). Much smaller diff in reality.
bq. Also, shutting down the cluster after every test method is an overkill.
This was intentional. I wanted to make sure that both tests started from a
clean-installation (not that system tables are already sitting there from the
previous test).
> 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
> Fix For: 4.11.0
>
> Attachments: PHOENIX-3757.001.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.3.15#6346)
