[ 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-addendum.patch Attaching addendum that fixes test failures. > 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-addendum.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)