phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK
Date Wed, 08 Jul 2015 02:16:04 GMT


James Taylor commented on PHOENIX-978:

[~elilevine] - there' an issue that [~tdsilva] discovered with allowing a view to extend the
base table's PK:

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:
>             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

View raw message