[
https://issues.apache.org/jira/browse/PHOENIX-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886548#comment-16886548
]
Chinmay Kulkarni commented on PHOENIX-5302:
-------------------------------------------
[~lhofhansl] I believe this should have been broken ever since we introduced
namespace-schema mapping since we used to create the HBase table for
SYSTEM.CATALOG even if the client-server namespace mapping was incompatible.
Thus, the HBase table would exist, however the metadata for the table itself
would not be written to SYSTEM.CATALOG yet, since it would exception out before
it could do so.
> 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
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.14#76016)
