[
https://issues.apache.org/jira/browse/HBASE-15112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302237#comment-15302237
]
Matt Warhaftig commented on HBASE-15112:
----------------------------------------
Eh, the following interfaces already extend
{{org.apache.hadoop.hbase.Coprocessor}} and would also need to have child
interfaces to handle software attributes:
* org.apache.hadoop.hbase.coprocessor.BulkLoadObserver
* org.apache.hadoop.hbase.coprocessor.EndpointObserver
* org.apache.hadoop.hbase.coprocessor.MasterObserver
* org.apache.hadoop.hbase.coprocessor.RegionObserver
* org.apache.hadoop.hbase.coprocessor.RegionServerObserver
* org.apache.hadoop.hbase.coprocessor.WALObserver
That makes my suggested approach even more inelegant. I would prefer waiting
until Java 8 to handle this through default method. If anyone has other
suggestions for patterns to approach this feature or wants to vote for the
current approach please comment.
> Allow coprocessors to extend 'software attributes' list
> -------------------------------------------------------
>
> Key: HBASE-15112
> URL: https://issues.apache.org/jira/browse/HBASE-15112
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Reporter: Nick Dimiduk
>
> Over on the {{/master-status}} and {{/rs-status}} pages we have a list of
> release properties, giving details about the cluster deployment. We should
> make this an extension point, allowing coprocessors to register information
> about themselves as well. For example, Phoenix, Trafodion, Tephra, &c might
> want to advertise installed version and build details as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
