[ https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217480#comment-16217480 ]
ASF GitHub Bot commented on PHOENIX-3757: ----------------------------------------- Github user twdsilva commented on a diff in the pull request: https://github.com/apache/phoenix/pull/277#discussion_r146662118 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java --- @@ -2905,14 +2918,18 @@ public void upgradeSystemTables(final String url, final Properties props) throws } } finally { if (acquiredMutexLock) { - releaseUpgradeMutex(mutexRowKey); + try { + releaseUpgradeMutex(mutexRowKey); + } catch (IOException e) { + logger.warn("Release of upgrade mutex failed ", e); --- End diff -- Is it ok to continue on if we fail to release the upgrade mutex, or should we just let the exception be thrown? > 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)