[
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401037#comment-16401037
]
James Taylor commented on PHOENIX-4579:
---------------------------------------
I don't think we need any new properties. Phoenix calls the
MetaDataProtocol.getVersion() which makes an RPC to the server. This is prior
to any attempts to create the SYSTEM.CATALOG. We need that to return the
current version of the SYSTEM.CATALOG (i.e. the PTable.getTimestamp() of that
row). Based on {{phoenix.autoupgrade.enabled}} being false, we can throw an
exception if an upgrade is required (but not being performed).
> 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)
