[
https://issues.apache.org/jira/browse/HBASE-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672007#comment-13672007
]
Andrew Purtell commented on HBASE-8607:
---------------------------------------
Another option is to consider external coprocessor hosts. Then a reload is a
process restart but involving only to the coprocessor / child JVM. That is
HBASE-4047.
> Run HBase server in an OSGi container
> -------------------------------------
>
> Key: HBASE-8607
> URL: https://issues.apache.org/jira/browse/HBASE-8607
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Reporter: James Taylor
>
> Run the HBase server in an OSGi container to support updating custom filters
> and coprocessor updates without requiring a region server reboot. Typically,
> applications that use coprocessors and custom filters also have shared
> classes underneath, so putting the burden on the user to include some kind of
> version name in the class is not adequate. Including the version name in the
> package might work in some cases (at least until dependent jars start to
> change as well), but is cumbersome and overburdens the app developer.
--
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
