Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Tue, 19 Dec 2017 23:50:00 +0000 (UTC)
From: "Thomas D'Silva (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13125699.1513626488000.498258.1513727400087@Atlassian.JIRA>
In-Reply-To: <JIRA.13125699.1513626488000@Atlassian.JIRA>
References: <JIRA.13125699.1513626488000@Atlassian.JIRA> <JIRA.13125699.1513626488421@jira-lw-us.apache.org>
Subject: [jira] [Updated] (PHOENIX-4468) Looking up a parent index table of
 a child view from a different client fails.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Dec 2017 23:50:04 -0000


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

Thomas D'Silva updated PHOENIX-4468:
------------------------------------
    Attachment: PHOENIX-4468-v3-4.x-HBase-0.98.patch

[~jamestaylor]

Sorry, I forgot to include a new file that I added that has a test for this. I also moved testReturnAllSequencesNotCalledForNoOpenConnections() from SequenceIT to this new test class since it was not being tested correctly since SequenceIT uses ConnectionQueryServicesTestImpl instead of ConnectionQueryServicesImpl.

I added a v3 patch that has the new test PhoenixDriverIT and also modified the javadoc to reference the JIRA. 

> Looking up a parent index table of a child view from a different client fails. 
> -------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4468
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4468
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Thomas D'Silva
>            Assignee: Thomas D'Silva
>             Fix For: 4.14.0, 4.13.2
>
>         Attachments: PHOENIX-4468-4.x-HBase-0.98.patch, PHOENIX-4468-v2-4.x-HBase-0.98.patch, PHOENIX-4468-v3-4.x-HBase-0.98.patch
>
>
> When you execute a query on a view, phoenix will use any indexes on the base table that have all the required columns. We create a new PTable based on the parent table index and tack on the view statement (to ensure we only see rows that we can access from the view). This PTable is added to the client side connection metadata cache. This table is not available on the server side (in SYSTEM.CATALOG).
> If you lookup the parent index table from a different client (that never ran a query on the view), it will fail with a TableNotFoundException.


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