[
https://issues.apache.org/jira/browse/PHOENIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710572#comment-16710572
]
Josh Elser commented on PHOENIX-5054:
-------------------------------------
{quote}The main drawback as you pointed out is this also requires the
SYSTEM.LOG feature being enabled.
{quote}
I think that's an OK compromise.
{quote}If you wanted to recreate the table/view somewhere else you would have
to run all the ddl statements
{quote}
We could certainly implement what I'm asking here using the data we'd have in
system.log; I think we should have something which can say "this is the DDL" at
some given time.
One other consideration is that if we implement this using SYSTEM.LOG, we'll
also have to do something fancier with age-off on the data (otherwise, we'll
get an incomplete picture).
> "look up" the `CREATE TABLE` statement used for a table
> -------------------------------------------------------
>
> Key: PHOENIX-5054
> URL: https://issues.apache.org/jira/browse/PHOENIX-5054
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Josh Elser
> Priority: Major
>
> This is a super common problem we run into:
> # User files report/complaint
> # We ask for DDLs for table and any indexes
> # We receive the output of `describe <table>` from the HBase shell
> Presumably, we have all of the necessary information inside of
> {{SYSTEM.CATALOG}}, we could recreate the {{CREATE TABLE}} statement for a
> table, no? I think it would be super helpful to, at a given point in time,
> obtain the {{CREATE TABLE}} statement to recreate a table as it currently
> exists.
> Split points might be the only thing we can't explicitly do via Phoenix, but
> that's pretty minor compared to everything else.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
