You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/23 21:54:00 UTC
[jira] [Commented] (PHOENIX-3757) System mutex table not being
created in SYSTEM namespace when namespace mapping is enabled
[ https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215917#comment-16215917 ]
ASF GitHub Bot commented on PHOENIX-3757:
-----------------------------------------
GitHub user karanmehta93 opened a pull request:
https://github.com/apache/phoenix/pull/277
PHOENIX-3757 System mutex table not being created in SYSTEM namespace…
… when namespace mapping is enabled
On fresh cluster with system table namespace mapping enabled, SYSMUTEX will be created in SYSTEM namespace directly.
It will be migrated to SYSTEM namespace if that property is enabled
The migrations also require locking in SYSMUTEX table since it disables and enables SYSCAT.
SYSCAT upgrades will acquire lock in appropriate SYSMUTEX table based on the client properties.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karanmehta93/phoenix PHOENIX-3757
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/277.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #277
----
commit 58c70f6ea46b76ed6474121b23e9756b7c5d9912
Author: Karan Mehta <ka...@gmail.com>
Date: 2017-10-23T21:44:21Z
PHOENIX-3757 System mutex table not being created in SYSTEM namespace when namespace mapping is enabled
----
> 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: Karan Mehta
> Priority: Critical
> Labels: namespaces
> Fix For: 4.13.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)