[
https://issues.apache.org/jira/browse/PHOENIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550857#comment-17550857
]
Istvan Toth edited comment on PHOENIX-6720 at 6/7/22 7:55 AM:
--------------------------------------------------------------
This should find the affected tables (on the source instance):
{noformat}
select * from system.catalog where column_qualifier is not null and
cast(cast(ordinal_position+9 as smallint) as varbinary)!=COLUMN_QUALIFIER
;{noformat}
(the above only applies for tables with column_qualifier=2)
was (Author: stoty):
This should find the affected tables (on the source instance):
{noformat}
select * from system.catalog where column_qualifier is not null and
cast(cast(ordinal_position+9 as smallint) as varbinary)!=COLUMN_QUALIFIER
;{noformat}
> "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,create table generate column qualifier order.
> When moving data between instances, and the original table had some columns
> removed, or swapped around, then the column qualifers in the table are not
> guarenteed to start from the expected value and increase by 1 for each
> column, based on the ordering of columns.
> This means that when we load a data table via HBase (i.e from a snaphsot),
> and then execute the DDL created by the show create table, or by other means,
> the column_qualifiers on the new table are going to point to the wrong Hbase
> cell.
> We need to accept and use COLUMN_QUALIFIER properties for columns, and
> include them in in the show create table output for column encoded tables.
> We also need to accept and generate QUALIFIER_COUNTER for the tables.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
