[PHOENIX-4806] make PhoenixStorageHander using only unmanaged tables

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.14.0, 5.0.0
• Assignee: Sergey Soldatov
• Reporter: Sergey Soldatov
• Created: 09/Jul/18 19:10
• Updated: 09/Jul/18 19:59

Description

For managed table Hive is heavily using internal statistic which is not updated properly when data is changing from outside. So all custom storage handlers are moving to the schema when only unmanaged (external) tables are using.
The suggested lifecycle:
1) All tables should be created with external keyword
2) if Phoenix table doesn't exist, we create a new one and add a flag that it should be deleted on drop table from hive
3) If Phoenix table exists, no changes in the existing behavior.

Some of the storage handlers that are part of Hive distribution are already using this schema. Others are in progress.

FYI elserj

Issue Links

• is related to: HIVE-19753 Strict managed tables mode in Hive