[
https://issues.apache.org/jira/browse/PHOENIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705287#comment-16705287
]
Josh Elser commented on PHOENIX-5054:
-------------------------------------
{quote}Would "!desc <tablename>" from sqlline be sufficient for what you're
looking for?
{quote}
Ehh, not nearly as easy to consume as the original SQL :). Also, this doesn't
seem to capture things like SALT_BUCKETS.
{quote}Should we just store the exact ddl statement that was used while
creating the table?
{quote}
I think that's a super-simple first step (easy and functional!), probably
breaks down if we consider ALTER statements (as Ankit alludes).
> "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)
