[
https://issues.apache.org/jira/browse/PHOENIX-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052467#comment-16052467
]
James Taylor commented on PHOENIX-1505:
---------------------------------------
Indexes on views are for updatable views that allow columns to be defined. It
wouldn't make sense to add them on read-only views - not sure if that's
enforced or not, but hopefully it is.
The complication in supporting other more complex queries in is tracking the
multiple parents such that a {{CREATE VIEW v AS SELECT * ...}} projects all the
right columns as the underlying tables metadata change. We have this ability in
the way we represent this in our underlying Phoenix table, but the code likely
makes some assumptions that a view has only a single parent. It's all very
doable - we just need someone to volunteer to do the work.
> Support defining a VIEW over multiple tables
> --------------------------------------------
>
> Key: PHOENIX-1505
> URL: https://issues.apache.org/jira/browse/PHOENIX-1505
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Labels: SFDC
>
> Our current view implementation only supports views over a single table. We
> should enhance this to support creating a view over multiple tables. For
> example: CREATE VIEW v AS SELECT * FROM DEPT d, EMPL e WHERE d.dept_id =
> e.dept_id
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
