You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2019/05/24 23:05:00 UTC

[jira] [Updated] (PHOENIX-5302) Different isNamespaceMappingEnabled for server / client causes TableNotFoundException

     [ https://issues.apache.org/jira/browse/PHOENIX-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas D'Silva updated PHOENIX-5302:
------------------------------------
    Fix Version/s: 5.1.0
                   4.15.0

> Different isNamespaceMappingEnabled for server / client causes TableNotFoundException
> -------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5302
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5302
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.2
>            Reporter: Vincent Poon
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>
> Scenario:
> 1)  Fresh cluster start with server isNamespaceMappingEnabled=true.
> 2)  Client connects with isNamespaceMappingEnabled=false.  Expected exception thrown ("Inconsistent namespace mapping")
> 3)  Client connects with isNamespaceMappingEnabled=true.  Exception: "Table undefined. tableName=SYSTEM.CATALOG"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)