[
https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617847#comment-14617847
]
James Taylor commented on PHOENIX-978:
--------------------------------------
[~elilevine] - there' an issue that [~tdsilva] discovered with allowing a view
to extend the base table's PK:
https://issues.apache.org/jira/browse/PHOENIX-2058?focusedCommentId=14617813&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14617813
It'll cause those rows to no longer be readable by the base table. This JIRA
will require more work - basically we'd need to no longer assume that we can
treat the remaining bytes in a row key as the value of the last column. This is
an optimization we do to prevent walking the row key to look for our separator
byte (for var length types only).
> Allow views to extend base table's PK
> -------------------------------------
>
> Key: PHOENIX-978
> URL: https://issues.apache.org/jira/browse/PHOENIX-978
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 3.0.0, 4.0.0
> Reporter: Eli Levine
> Assignee: Eli Levine
> Fix For: 5.0.0, 4.5.0
>
> Attachments: PHOENIX-978.diff
>
>
> CREATE VIEW syntax currently disallows PK constraint to be defined. As a
> result views and tenant-specific tables created using CREATE VIEW
> automatically inherit their base table's PK with no way to extend it.
> Base tables should be allowed to be created with a minimum of PK columns to
> support views, and views to extend PKs as desired. This would allow a single
> base table to support a heterogeneous set of views on top of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
