[jira] [Commented] (BIGTOP-1007) Introduce a modules system for HBase coprocessor applications

["Roman Shaposhnik (JIRA)" <ji...@apache.org>]

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

Roman Shaposhnik commented on BIGTOP-1007:
------------------------------------------

Andrew, I'm not that familiar with co-processor in HBase. Could you please elaborate on what kind of files are you expecting to be dropped into /etc/hbase/modules.d?

Basically, if you could walk us through a scenario of using this proposed feature -- that would be greatly appreciated!
                
> Introduce a modules system for HBase coprocessor applications
> -------------------------------------------------------------
>
>                 Key: BIGTOP-1007
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1007
>             Project: Bigtop
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>
> Consider a modules system convention ("/etc/hbase/modules.d"), a common pattern used for example by Apache httpd, for easily installation and removal of HBase coprocessor applications.
> Within the modules.d/ directory, one additional level of subdirectories can be created, into which a package can drop site xml fragments and scripts to execute after regionserver and master (re)start. Future packages that ship an HBase coprocessor application could then add configuration bits without concern about collisions and trigger a regionserver reload in postinstall.
> HBase already ships a tool for merging configuration files. Changes required for this will be proposed upstream if needed.

--
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