phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janos Gub (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-4800) Multiple phoenix tables can be created for the same HBase table.
Date Fri, 29 Jun 2018 12:55:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527582#comment-16527582
] 

Janos Gub edited comment on PHOENIX-4800 at 6/29/18 12:54 PM:
--------------------------------------------------------------

In cases where namespace mapping is not enabled both tables will be created in the default
namespace. Thus the two tables will point to the same physical table in HBase. Also I am not
propagating the usage of . in the name of the tables, I am just stating that phoenix does
not really help if the user somehow did it.


was (Author: gubjanos):
In cases where namespace mapping is not enabled both tables will be created in the default
namespace. Thus the two tables will point to the same physical table in HBase.

> Multiple phoenix tables can be created for the same HBase table.
> ----------------------------------------------------------------
>
>                 Key: PHOENIX-4800
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4800
>             Project: Phoenix
>          Issue Type: Bug
>         Environment: phoenix master 6acdae0ff1a63980f40fe1b794d40ab949cc423d with hbase
branch-1.4 defe97edb9f95600ec44525c47a2b23da643da2a
>            Reporter: Janos Gub
>            Priority: Major
>
> While namespace mapping is disabled the following two tables can be created and will
point to the same hbase table:
> CREATE TABLE A.B (x INTEGER PRIMARY KEY);
> CREATE TABLE "A.B" (y varchar PRIMARY KEY);
> It is because MetaDataEndpointImpl will determine if a table is created by checking
the presence of the byte table key in the metadata cache. But the byte key for A.B is 00410042
and the byte key for "A.B" is 0041e242. 
> This causes other issues I will link to this ticket.



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

Mime
View raw message