[
https://issues.apache.org/jira/browse/PHOENIX-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543050#comment-17543050
]
ASF GitHub Bot commented on PHOENIX-6719:
-----------------------------------------
gjacoby126 commented on PR #1448:
URL: https://github.com/apache/phoenix/pull/1448#issuecomment-1139908096
Note: the test that detected this is in a draft of phoenix-connectors'
PHOENIX-5517 / PHOENIX-5448 (CDC message producer and Avro serialization). The
test will be contributed when those JIRAs are contributed.
> 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
> Priority: Major
> 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)
