[
https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961529#comment-15961529
]
Samarth Jain commented on PHOENIX-3757:
---------------------------------------
[~elserj] - It seems like the new test class that you added is being picked up
by surefire for execution. For ex - see the test results report that HadoopQA
generated. It is likely because the test class SystemTablePermissionsIT is not
extending one of the known base classes which is used by surefire to figure out
test classes to run. You would probably need to extend
BaseUniqueNamesOwnClusterIT and override the @After and @AfterClass methods
appropriately.
> 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, 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.3.15#6346)
