[
https://issues.apache.org/jira/browse/PHOENIX-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-1306.
-----------------------------------
Resolution: Won't Fix
Turns out this isn't necessary. An easy way to accomplish this is to set the
CURRENT_SCN connection property to a timestamp earlier than any cell timestamp
for the table. This will prevent any empty key values from being added to the
table at create time.
> Option in CREATE TABLE & CREATE INDEX clauses to indicate that underlying
> table is already a phoenix table
> ----------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1306
> URL: https://issues.apache.org/jira/browse/PHOENIX-1306
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Krishna
>
> When a HBase table is converted to Phoenix table (through CREATE TABLE or
> CREATE INDEX statements), Phoenix will do an upsert for each rowkey for
> column qualifier "_0". If the underlying HBase table is already in Phoenix
> format, there is no need to redo the upsert.
> Provide an option in relevant Phoenix DDLs to specify if the underlying HBase
> table is already in Phoenix format. This will ensure, Phoenix does not redo
> the upsert statements during the DDL.
> CREATE TABLE and CREATE INDEX are two examples of such DDLs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
