[
https://issues.apache.org/jira/browse/PHOENIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544338#comment-17544338
]
Istvan Toth commented on PHOENIX-6720:
--------------------------------------
This is not just a show create table issue, unless we accept explicit
COLUMN_QUALIFIERs in the create table statements, there is no way to re-create
such tables in phoenix from DDL statements. (Still need we check if can specify
CQs)
> show create table can't recreate column encoded tables that had columns
> dropped
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-6720
> URL: https://issues.apache.org/jira/browse/PHOENIX-6720
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Istvan Toth
> Priority: Major
>
> For column encoded tables, show create table will simply list the columns in
> order.
> When the original table had some columns removed, or swapped around, then the
> column qualifers in the table are not guarenteed to start from 0 and increase
> by 1 for each column, based on the ordering of columns.
> This means that when we load a data table via HBase, and then execute the DDL
> created by the show create table, the column_qualifiers on the new table are
> going to point to the wrong Hbase cell.
> We need to include the COLUMN_QUALIFIERs in the show create table output for
> column encoded tables, (and we need to accept those as well, if don't already
> do that.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
