[
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399766#comment-16399766
]
James Taylor commented on PHOENIX-4579:
---------------------------------------
Because we always attempt to create the system catalog table, the code that
creates/updates the hbase metadata always runs. So even if the table already
exists (determined on the server by the createTable call), the metadata would
have already been updated.
I don't think we need a new {{phoenix.system.upgrade.first.connection}}
property. Instead, we can base what we do off of
{{phoenix.autoupgrade.enabled}} and the version of the system catalog (i.e. the
new information we'll return in the response back from the getVersion() call).
Like you said, if {{phoenix.autoupgrade.enabled}} is false and the version we
get back is older than the current client version, we can throw an error
(unless we're in the process of upgrading). At that point, the old action a
client could take would be to run EXECUTE 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)
