[
https://issues.apache.org/jira/browse/PHOENIX-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454846#comment-16454846
]
James Taylor commented on PHOENIX-4709:
---------------------------------------
Please review, [~tdsilva]. Would be good to get your feedback too,
[~ckulkarni]. If there are older clients running when the upgrade occurs, the
metadata properties will get set back unfortunately. Not sure we can do
anything about that. If there aren't then it would be updated (and stay
updated). So it seems worth doing. WDYT?
> Alter split policy in upgrade path for system tables
> ----------------------------------------------------
>
> Key: PHOENIX-4709
> URL: https://issues.apache.org/jira/browse/PHOENIX-4709
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Priority: Major
> Attachments: PHOENIX-4709_v1.patch
>
>
> With PHOENIX-4700, the split policy would only change for new installations.
> For existing installations, the schema of system tables only changes in the
> upgrade path, including for HBase metadata now. Thus we need an ALTER TABLE
> call in our upgrade path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
