[
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-1367-4.x-HBase-0.98-v4.patch
I have attached a v4 patch.
I didn't use a static constant prefix while renaming the child view index, so
that we can support having two child views with different view statements
(since the view name is unique we can add both view indexes with different view
statements to the cache).
I modified PTable.getParentSchemaName() and getParentTableName() and changed
getParentName() to only return the physical names for views.
I checked where we use
getParentName()/getParentSchemaName()/getParentTableName() and I think we
should be good. The tests all pass as well.
> 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-1367-4.x-HBase-0.98-v3.patch,
> PHOENIX-1367-4.x-HBase-0.98-v4.patch, 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)
