[PHOENIX-1508] VIEW enhancements

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Assignee: Unassigned
• Reporter: James R. Taylor
• Created: 05/Dec/14 02:11
• Updated: 24/Jan/16 03:25

Sub-Tasks

• VIEW derived from another VIEW doesn't use parent VIEW indexes: Closed
• Minimize projection into scan for VIEW: Resolved
• Allow arbitrary SELECT expressions in VIEW definition: Open
• Support defining a VIEW over multiple tables: Open
• VIEW indexes are not kept in sync when parent table updated directly: Open
• Support adding column to a table that has views: Closed
• Allow views to extend base table's PK (only if last PK column is fixed length): Closed
• Automatically add columns added to a view to all its child views: Open
• Allow views to extend base table's PK even if last PK col is variable lengthnly if last PK column is fixed length): Open
• Link record is in the format CHILD-PARENT for phoenix views and it has to scan the entire table to find the parent suffix.: Resolved
• Support drop of column from table with views: Closed
• Support append only schema declaration: Closed
• Support auto partition for views: Closed
• Implement PTable.getParentName() correctly for views: Resolved
• Disallow creation of index on table/view with child views: Open
• Only mark view as updatable if rows cannot overlap with other updatable views: Resolved
• Adding a pk column to a base table that has a child view that has added its own pk column of a different data type should not be allowed: Open
• Upserting rows into child views with pk fails when the base view has an index on it.: Resolved