[
https://issues.apache.org/jira/browse/HBASE-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671896#comment-13671896
]
James Taylor commented on HBASE-8607:
-------------------------------------
My thinking is that an OSGi container would allow a new version of a
coprocessor (and/or custom filter) jar to be loaded. Class conflicts between
the old jar and the new jar would no longer be a problem - you'd never need to
unload the old jar. Instead, future HBase operations that invoke the
coprocessor would cause the newly loaded jar to be used instead of the older
one. I'm not sure if this is possible or not. The whole idea would be to
prevent a rolling restart or region close/reopen.
> 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
