You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Janos Gub (JIRA)" <ji...@apache.org> on 2018/06/29 12:37:00 UTC
[jira] [Commented] (PHOENIX-4800) Multiple phoenix tables can be
created for the same HBase table.
[ https://issues.apache.org/jira/browse/PHOENIX-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527566#comment-16527566 ]
Janos Gub commented on PHOENIX-4800:
------------------------------------
Also I would like to work on this issue. Could you please add me to the contributors [~elserj]?
My first way of solving this issue would be to restrict the usage of . in schema and table names.
> 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)