[
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400956#comment-16400956
]
Thomas D'Silva commented on PHOENIX-4579:
-----------------------------------------
[~jamestaylor]
Should we remove the default behavior of automatically upgrading and make the
upgrade a manual step that requires the user to run "EXECUTE UPGRADE" ?
Currently if {{phoenix.autoupgrade.enabled}} is false and an upgrade is
required the user is not allowed to execute a query other than "EXECUTE
UPGRADE".
Then we can just have a config that determines whether or not we always attempt
to create the system catalog table. If this config is true and the system
catalog table does not exists we throw an exception. If it exists we make the
rpc to the server which will return the timestamp of the SYSTEM.CATALOG from
the server which we can use to determine if we need to upgrade.
> Add a config to conditionally create Phoenix meta tables on first client
> connection
> -----------------------------------------------------------------------------------
>
> Key: PHOENIX-4579
> URL: https://issues.apache.org/jira/browse/PHOENIX-4579
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Mujtaba Chohan
> Assignee: Chinmay Kulkarni
> Priority: Major
> Attachments: PHOENIX-4579.patch
>
>
> Currently we create/modify Phoenix meta tables on first client connection.
> Adding a property to make it configurable (with default true as it is
> currently implemented).
> With this property set to false, it will avoid lockstep upgrade requirement
> for all clients when changing meta properties using PHOENIX-4575 as this
> property can be flipped back on once all the clients are upgraded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
