[
https://issues.apache.org/jira/browse/PHOENIX-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-347:
---------------------------------
Assignee: (was: mujtaba)
> Improve Phoenix install process
> -------------------------------
>
> Key: PHOENIX-347
> URL: https://issues.apache.org/jira/browse/PHOENIX-347
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
>
> With the resolution of
> [HBASE-1936](https://issues.apache.org/jira/browse/HBASE-1936) we can now
> create an install script/ui for Phoenix that will:
> * copy the phoenix-<major>.<minor version>.jar into HDFS
> * create/replace an HDFS symlink of 'phoenix-latest.jar' at a known location
> to point to the new jar
> * use this path as the jar path for Phoenix coprocessors
> * upgrade the jar path of existing HTables on start up (see
> ConnectionQueryServicesImpl.upgradeTablesFrom0_94_2to0_94_4 for an example)
> * define a Phoenix specific property that overrides the default location (or
> just uses null for the jar path). This will be useful for a local build
> and/or test environments.
> If it's a new install, Phoenix will just start working (which is cool). If
> it's an upgrade, then a rolling restart of the cluster will be required in
> order to start using the new jar (which seems like the best we can do).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
