[
https://issues.apache.org/jira/browse/PHOENIX-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-3174:
----------------------------------
Attachment: PHOENIX-3174_v3_master.patch
Updated patch that introduces a new EXECUTE UPGRADE statement. For now, by
default, we allow phoenix clients to automatically run upgrades. It can be
controlled by setting phoenix.autoupgrade.enable to false in the
hbase-site.xml. When a new client connects to the cluster, it isn't able to
execute any SQL unless EXECUTE UPGRADE is run to upgrade the metadata. To make
sure Phoenix's internal background services like index rebuild and tracing
still work, I have changed the code to use HBase or lower level Phoenix API.
For ex - for tracing, I changed it use a lower level API (MutationPlan and
MutationState) so that traces could still be inserted into the trace table.
[~jamestaylor] - please review.
> Make minor upgrade a manual step
> --------------------------------
>
> Key: PHOENIX-3174
> URL: https://issues.apache.org/jira/browse/PHOENIX-3174
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Samarth Jain
> Fix For: 4.9.0, 4.8.1
>
> Attachments: PHOENIX-3174.patch, PHOENIX-3174_v2.patch,
> PHOENIX-3174_v3_master.patch
>
>
> Instead of automatically performing minor release upgrades to system tables
> in an automated manner (on first connection), we should make upgrade a
> separate manual step. If a newer client attempts to connect to a newer server
> without the upgrade step having occurred, we'd fail the connection.
> Though not as automated, this would give users more control and visibility
> into when an upgrade over system tables occurs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
