You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2022/07/12 07:55:00 UTC

[jira] [Updated] (PHOENIX-6720) "create table" can't recreate column encoded tables that had columns dropped

     [ https://issues.apache.org/jira/browse/PHOENIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Istvan Toth updated PHOENIX-6720:
---------------------------------
    Priority: Blocker  (was: Major)

> "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: Blocker
>
> 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.10#820010)