[
https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218952#comment-16218952
]
ASF GitHub Bot commented on PHOENIX-3757:
-----------------------------------------
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/277#discussion_r146901856
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
---
@@ -2514,7 +2529,7 @@ private void createSysMutexTable(HBaseAdmin admin)
throws IOException, SQLExcept
return
Lists.newArrayList(admin.listTableNames(QueryConstants.SYSTEM_SCHEMA_NAME +
"\\..*"));
}
- private void createOtherSystemTables(PhoenixConnection metaConnection)
throws SQLException {
+ private void createOtherSystemTables(PhoenixConnection metaConnection,
HBaseAdmin hBaseAdmin) throws SQLException {
--- End diff --
nit: s/hBaseAdmin/hbaseAdmin/ camel-case typically isn't observed on
"hbase" ;)
> 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,
> PHOENIX-3757.003.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)