[
https://issues.apache.org/jira/browse/PHOENIX-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849155#comment-16849155
]
Lars Hofhansl commented on PHOENIX-5302:
----------------------------------------
Is this new behavior as of 4.15, or was that broken in 4.14.x already?
> 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
> Assignee: Chinmay Kulkarni
> 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)
