Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Sat, 21 Oct 2017 21:50:02 +0000 (UTC)
From: "Karan Mehta (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13104478.1506153151000.28228.1508622602476@Atlassian.JIRA>
In-Reply-To: <JIRA.13104478.1506153151000@Atlassian.JIRA>
References: <JIRA.13104478.1506153151000@Atlassian.JIRA> <JIRA.13104478.1506153151747@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (PHOENIX-4227) Row for "SYSTEM" schema is not
 created during ConnectionQueryServicesImpl init
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 21 Oct 2017 21:50:10 -0000


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

Karan Mehta reassigned PHOENIX-4227:
------------------------------------

    Assignee: Karan Mehta

> Row for "SYSTEM" schema is not created during ConnectionQueryServicesImpl init 
> -------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4227
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4227
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.12.0
>            Reporter: Karan Mehta
>            Assignee: Karan Mehta
>
> For every new schema created through Phoenix, a row containing the schema name (with a 0x0 at the beginning and the end) is added to SYSTEM.CATALOG table. This is used for by other statements such as "USE SCHEMA" or "CREATE SCHEMA" to determine if the schema exists or not. 
> However when we turn on namespaces, SYSTEM tables are automatically migrated to SYSTEM namespace in HBase. However an SYSTEM.CATALOG entry with the row (\x0SYSTEM\x0) is not created. Thus other statements trying to use it might receive a SCHEMA_NOT_FOUND_EXCEPTION even though the schema exists in the file.
> A "CREATE SCHEMA SYSTEM" statement can create the corresponding row entry in the SYSCAT table. This JIRA is to fix this behaviour and make it consistent for all schemas across Phoenix.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)