[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954487#comment-15954487 ] Josh Elser commented on PHOENIX-3756: - Thanks for taking a look, James! bq. is there a possibility

Re: Indexes and RegionNormalizer?

Though I don't think it's been tested, I can't think of any reasons why it wouldn't just work. You'd need to enable the RegionNormalizer for the index table in the case of global indexes since they're separate, orthogonal HBase tables (i.e. enabling for the data table wouldn't cause it to carry

Indexes and RegionNormalizer?

Hi all, I'm wondering, when activating the RegionNormalizer, is there any impact on a table indexes? Is that compatible? Thanks, JMS

[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954165#comment-15954165 ] Hadoop QA commented on PHOENIX-3756: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954146#comment-15954146 ] James Taylor commented on PHOENIX-3756: --- Patch looks good to me, but maybe one possible issue: is

[jira] [Updated] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-3756: Attachment: PHOENIX-3756.004.patch .004 Tries to make the catches for AccessDeniedException a bit

[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=15953999#comment-15953999 ] Samarth Jain commented on PHOENIX-3757: --- +1 to being consistent and having SYSTEM.MUTEX in the

[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=15953983#comment-15953983 ] Andrew Purtell commented on PHOENIX-3757: - Shouldn't all tables named "SYSTEM" be in the SYSTEM

[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=15953905#comment-15953905 ] Josh Elser commented on PHOENIX-3757: - bq. I am curious though as to what issue are you running into

[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=15953899#comment-15953899 ] Samarth Jain commented on PHOENIX-3757: --- Yeah, I remember making this change. SYSTEM.MUTEX table

[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=15953882#comment-15953882 ] Josh Elser commented on PHOENIX-3757: - FYI [~samarthjain], [~ankit.singhal] WRT PHOENIX-3726. It

[jira] [Resolved] (PHOENIX-3754) The query in the Getting Started page fails (OutOfOrderScannerNextException)

[ https://issues.apache.org/jira/browse/PHOENIX-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-3754. - Resolution: Invalid > The query in the Getting Started page fails

[jira] [Commented] (PHOENIX-3754) The query in the Getting Started page fails (OutOfOrderScannerNextException)

[ https://issues.apache.org/jira/browse/PHOENIX-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953715#comment-15953715 ] Josh Elser commented on PHOENIX-3754: - [~smizy], re-read that exception message :) {noformat}

[jira] [Created] (PHOENIX-3758) PhoenixMetricsIT#testGlobalPhoenixMetricsForQueries fails intermittently

Sneha Kanekar created PHOENIX-3758: -- Summary: PhoenixMetricsIT#testGlobalPhoenixMetricsForQueries fails intermittently Key: PHOENIX-3758 URL: https://issues.apache.org/jira/browse/PHOENIX-3758