[
https://issues.apache.org/jira/browse/HBASE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630707#comment-13630707
]
James Taylor commented on HBASE-1936:
-------------------------------------
Thanks for the back port, [~jxiang]. I'm thinking Phoenix will primary leverage
this to make it easier for folks to get up and running. Currently, we require
the phoenix jar to manually be copied to every region server and placed on the
HBase classpath. Instead, if I understand this enhancement correctly, at
install time we can:
- 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 both coprocessors and filters (THIS PART
WASN'T POSSIBLE BEFORE)
- do a rolling restart of the cluster to start using the new jar
We'd still need the rolling restart, because we'd need the classes from the old
version unloaded and the classes from the new version loaded.
Does this sound accurate? Thanks
> ClassLoader that loads from hdfs; useful adding filters to classpath without
> having to restart services
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1936
> URL: https://issues.apache.org/jira/browse/HBASE-1936
> Project: HBase
> Issue Type: New Feature
> Reporter: stack
> Assignee: Jimmy Xiang
> Labels: noob
> Fix For: 0.98.0, 0.95.1
>
> Attachments: 0.94-1936.patch, cp_from_hdfs.patch,
> HBASE-1936-trunk(forReview).patch, trunk-1936.patch, trunk-1936_v2.1.patch,
> trunk-1936_v2.2.patch, trunk-1936_v2.patch, trunk-1936_v3.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
