[
https://issues.apache.org/jira/browse/PHOENIX-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362738#comment-14362738
]
James Taylor commented on PHOENIX-1550:
---------------------------------------
[~sunfl] - didn't know this was so high on your list. What else is on that list?
FWIW, if you had a flag or property passed through the CREATE TABLE call that
told Phoenix not to insert the empty key value on all rows, you could use
snapshot/restore (+ CREATE TABLE) pretty easily, no? It'd be < 20 lines of code.
> Freeze and thaw Phoenix tables
> ------------------------------
>
> Key: PHOENIX-1550
> URL: https://issues.apache.org/jira/browse/PHOENIX-1550
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> HBase snapshots provide a way to freeze the state of a table and then later
> restore that state from the snapshot or clone it into a new table. This can
> be very convenient for a wide range of use cases. However, we can't apply
> this technique directly to Phoenix tables because Phoenix generates and uses
> more state in more locations than a basic HBase table - a Phoenix table may
> have one or more secondary indexes, global or local, schema in the system
> catalog, sequence state, statistics.
> This issue is about considering a freeze and thaw feature for Phoenix tables,
> perhaps based on HBase snapshots. A freeze operation would create a
> consistent point in time snapshot of a Phoenix table and all related index
> data and metadata. A thaw operation would restore frozen state either by
> overwriting the table or by cloning the state into a new table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
