You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2018/12/03 17:10:00 UTC
[jira] [Commented] (PHOENIX-5054) "look up" the `CREATE TABLE`
statement used for a table
[ https://issues.apache.org/jira/browse/PHOENIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707541#comment-16707541 ]
Josh Elser commented on PHOENIX-5054:
-------------------------------------
{quote}See also PHOENIX-4286 for a similar idea (which I've alas never had bandwidth to implement.)
{quote}
Thanks Geoffrey. The migration use-case you mention is also a really good reason for us to try to build this. No worries on the lack of time to actually build it, we all suffer from that problem ;)
> "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)