hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8607) Run HBase server in an OSGi container
Date Sun, 02 Jun 2013 01:37:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672287#comment-13672287
] 

Andrew Purtell commented on HBASE-8607:
---------------------------------------

Something might worth trying out is an OSGi socket as coprocessor. Like with HBASE-4047 where
one side of the umbilical is a "normal" coprocessor, here that is instead a shim for another
piece of code that is (re)loaded as a bundle. Would give us a sense of how workable embedding
an OSGi runtime and reloading a coprocessor might be. 
                
> 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

Mime
View raw message