[ https://issues.apache.org/jira/browse/PHOENIX-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas D'Silva updated PHOENIX-1367: ------------------------------------ Attachment: PHOENIX-1369-4.x-HBase-0.98-v3.patch [~jamestaylor] I have attached a modified patch based on the review feedback. I added a test testGlobalIndexOnSpecializedChildViews which verifies if there is a child view that is not present in the global view index it is not used. I think we don't need to modify getParentName() to return the physicalName if the parentName is null for b/w compatibility since MetaDataClient.addIndexesFromParentTable is called on the client and I added the following check {code} String parentName = view.getParentName()!=null ? view.getParentName().getString() : view.getPhysicalName().getString(); {code} > VIEW derived from another VIEW doesn't use parent VIEW indexes > -------------------------------------------------------------- > > Key: PHOENIX-1367 > URL: https://issues.apache.org/jira/browse/PHOENIX-1367 > Project: Phoenix > Issue Type: Sub-task > Reporter: James Taylor > Assignee: Thomas D'Silva > Fix For: 4.9.0, 4.8.1 > > Attachments: PHOENIX-1369-4.x-HBase-0.98-v2.patch, > PHOENIX-1369-4.x-HBase-0.98-v3.patch, PHOENIX-1369-4.x-HBase-0.98.patch, > PHOENIX_1367.test.patch > > > If a VIEW has an index and another VIEW is derived from it, the child view > will not use the parent view's indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)