[ https://issues.apache.org/jira/browse/PHOENIX-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kulkarni updated PHOENIX-6134: -------------------------------------- Description: Having such an option is useful when doing a Phoenix rollback on a cluster, doing metadata fixes such as manual changes to SYSTEM.CATALOG, etc. It provides more power to server-side operators to if they're able to explicitly block DDLs in order to prevent metadata from being in an inconsistent state. All changes for this should be on the server-side so that we can block DDLs even from older clients. was: Having such an option is useful when doing a Phoenix rollback on a cluster, doing metadata fixes such as manual changes to SYSTEM.CATALOG, etc. It provides more power to server-side operators to if they're able to explicitly block DDLs in order to prevent metadata from being in an inconsistent state. > Provide a server-side configuration to disallow all DDLs > -------------------------------------------------------- > > Key: PHOENIX-6134 > URL: https://issues.apache.org/jira/browse/PHOENIX-6134 > Project: Phoenix > Issue Type: New Feature > Affects Versions: 5.0.0, 4.15.0 > Reporter: Chinmay Kulkarni > Priority: Major > Fix For: 5.1.0, 4.16.0 > > > Having such an option is useful when doing a Phoenix rollback on a cluster, > doing metadata fixes such as manual changes to SYSTEM.CATALOG, etc. > It provides more power to server-side operators to if they're able to > explicitly block DDLs in order to prevent metadata from being in an > inconsistent state. > All changes for this should be on the server-side so that we can block DDLs > even from older clients. > -- This message was sent by Atlassian Jira (v8.3.4#803005)