[
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398045#comment-16398045
]
Thomas D'Silva commented on PHOENIX-4579:
-----------------------------------------
[~jamestaylor]
Whenever a client connect we try to create SYSTEM.CATALOG, but on the server if
the current table timestamp matches the timestamp of the mutations sent from
the client we return a newer table found and don't change the table properties.
I was trying to understand how when we set KEEP_DELETED_CELLS to false
(manually using sqline or HBase shell) it was getting set back to true. Do you
know how that happened?
> 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: Mujtaba Chohan
> 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)
