phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-4468) Looking up a parent index table of a child view from a different client fails.
Date Tue, 19 Dec 2017 23:50:00 GMT


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


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:
>             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,
> 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

View raw message