[jira] [Resolved] (PHOENIX-6584) Annotate HBase WALs with Schema Id
[ https://issues.apache.org/jira/browse/PHOENIX-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved PHOENIX-6584. --- Resolution: Implemented > Annotate HBase WALs with Schema Id > -- > > Key: PHOENIX-6584 > URL: https://issues.apache.org/jira/browse/PHOENIX-6584 > Project: Phoenix > Issue Type: Sub-task >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Major > > PHOENIX-5435 introduced WAL annotation with a tuple of fields (tenant, > Phoenix schema, table, and last DDL timestamp) to identify the Phoenix object > which had created an HBase edit, for use in change detection systems. > PHOENIX-6227 introduces the ability to store schema information about Phoenix > metadata in an external schema registry and save a lookup id to get the > metadata back. > Switch the WAL annotations to use this schema id rather than the existing > tuple. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (PHOENIX-6584) Annotate HBase WALs with Schema Id
[ https://issues.apache.org/jira/browse/PHOENIX-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby resolved PHOENIX-6584. -- Resolution: Fixed This was done as part of PHOENIX-6227, so resolving the subtask JIRA > Annotate HBase WALs with Schema Id > -- > > Key: PHOENIX-6584 > URL: https://issues.apache.org/jira/browse/PHOENIX-6584 > Project: Phoenix > Issue Type: Sub-task >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Major > Fix For: 4.17.0, 5.2.0 > > > PHOENIX-5435 introduced WAL annotation with a tuple of fields (tenant, > Phoenix schema, table, and last DDL timestamp) to identify the Phoenix object > which had created an HBase edit, for use in change detection systems. > PHOENIX-6227 introduces the ability to store schema information about Phoenix > metadata in an external schema registry and save a lookup id to get the > metadata back. > Switch the WAL annotations to use this schema id rather than the existing > tuple. -- This message was sent by Atlassian Jira (v8.20.1#820001)
