[jira] [Commented] (PHOENIX-5054) "look up" the `CREATE TABLE` statement used for a table

["Xinyi Yan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906694#comment-16906694 ] 

Xinyi Yan commented on PHOENIX-5054:
------------------------------------

I purposed clone table feature on PHOENIX-5431, and it seems a similar idea of this JIRA and PHOENIX-4286. What's the current status of this JIRA? I didn't see any update at PHOENIX-5034, which logs all critical statements to SYSTEM.LOG. If SYSTEM.LOG is enabled, we can easily get information from SYSTEM.LOG. If we don't pursue the SYSTEM.LOG option, I can try to implement with a combination of SYSTEM.CATALOG and HBase API to get metadata, such as replication_scope, etc. Any suggestion? Thanks in advance!

 

> "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.14#76016)