[
https://issues.apache.org/jira/browse/PHOENIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709501#comment-16709501
]
Karan Mehta commented on PHOENIX-5054:
--------------------------------------
[~elserj] [~gjacoby] [~vincentpoon] [~tdsilva]
Do you guys think if we can merge this with PHOENIX-5034? We can just audit the
whole history instead of creating the statement (where we might miss
something)? We have an internal tool that audits the schema and I believe that
this will be a good feature to push inside the phoenix-core as well.
FYI [~xucang]
> "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)
