[ https://issues.apache.org/jira/browse/PHOENIX-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224759#comment-17224759 ]
Viraj Jasani edited comment on PHOENIX-5586 at 11/2/20, 3:55 PM: ----------------------------------------------------------------- As part of PHOENIX-6125, we have new split policy introduced for SYSTEM.TASK which for now is just extending DisabledRegionSplitPolicy. As part of an upgrade to 4.16/5.1, updating split policy will be taken care of unless it was already updated manually. Hence, before 4.16/5.1 upgrade, if operator has already manually updated split policy of SYSTEM.TASK, an exception will be thrown during upgrade to 4.16 which would mandate an operator intervention to perform: # Merging SYSTEM.TASK regions into one single region (if multiple regions were already available before 4.16/5.1 upgrade) # Remove split policy of the table manually. was (Author: vjasani): As part of PHOENIX-6125, we have new split policy introduced for SYSTEM.TASK which for now is just extending DisabledRegionSplitPolicy. Before 4.16 upgrade, if operator has already manually updated split policy of SYSTEM.TASK, an exception will be thrown during upgrade to 4.16 which would mandate an operator intervention by merging SYSTEM.TASK regions into one single region (if multiple regions were already available before 4.16 upgrade) and also remove split policy of the table manually. > Add documentation for Splittable SYSTEM.CATALOG > ----------------------------------------------- > > Key: PHOENIX-5586 > URL: https://issues.apache.org/jira/browse/PHOENIX-5586 > Project: Phoenix > Issue Type: Improvement > Affects Versions: 4.15.0, 5.1.0 > Reporter: Chinmay Kulkarni > Priority: Blocker > Fix For: 4.15.1, 5.1.1, 4.16.0 > > > There are many changes after PHOENIX-3534 especially for backwards > compatibility. There are additional configurations such as > "phoenix.allow.system.catalog.rollback" which allows rollback of splittable > SYSTEM.CATALOG, etc. We should document these changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)