phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5302) Different isNamespaceMappingEnabled for server / client causes TableNotFoundException
Date Wed, 24 Jul 2019 22:34:00 GMT

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

Chinmay Kulkarni updated PHOENIX-5302:
--------------------------------------
    Attachment: PHOENIX-5302-4.14-HBase-1.3-v3.patch

> 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, 4.14.3
>
>         Attachments: PHOENIX-5302-4.14-HBase-1.3-v1.patch, PHOENIX-5302-4.14-HBase-1.3-v3.patch,
PHOENIX-5302-master.patch, Phoenix-5302-4.x-HBase-1.3-v1.patch
>
>          Time Spent: 50m
>  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)

Mime
View raw message