You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2022/05/27 17:34:00 UTC

[jira] [Created] (PHOENIX-6719) Duplicate Salt Columns in Schema Registry after ALTER

Geoffrey Jacoby created PHOENIX-6719:
----------------------------------------

             Summary: Duplicate Salt Columns in Schema Registry after ALTER
                 Key: PHOENIX-6719
                 URL: https://issues.apache.org/jira/browse/PHOENIX-6719
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 5.2.0
            Reporter: Geoffrey Jacoby
            Assignee: Geoffrey Jacoby
             Fix For: 5.2.0


When a table or view is change-detection enabled, we have to update the schema registry each time the schema is ALTERed. This is done by calculating the old PTable and applying the changed metadata edits to create a new PTable, which gets exported to the schema registry.

There's a bug in this calculation logic for salted tables, where the virtual salt column is on the old PTable, but gets added by the Builder logic of the new PTable. The result is an incorrect PTable (and schema) with an extra salt column. 

I discovered this while testing on a draft of PHOENIX-5517. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)