[
https://issues.apache.org/jira/browse/PHOENIX-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cody Marcel updated PHOENIX-1367:
---------------------------------
Attachment: PHOENIX_1367.test.patch
The attachment is only a test, but an actual patch.
I have noticed this effects not only the view, but also writes to the index on
the base view.
test scenario
--create table
--create view1 on base table
--create index on view1
--create view2 on view1.
--insert rows into view1
--insert rows into view2
--queries on view1 use the index as expected.
--queries on view2 do not use the index as described in this bug.
-- rows returned from query to view2 include all rows written to both views,
but only because they are returned from the base table instead of the index.
--rows returned from index/view1 do not reflect data written into view2. This
shows that the write path to the index on views of views is not kept in sync
with the base table.
> 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
> Attachments: 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)
