[
https://issues.apache.org/jira/browse/HBASE-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569214#comment-13569214
]
Andrew Purtell commented on HBASE-7738:
---------------------------------------
bq. Looks like HBASE-2677 is a better place for that larger fix.
I would agree, and changing path mapping can be done independent of any
new/better representations, though that makes sense to do too, especially if we
can cut the cord to the old types given the "singularity" rationale. The REST
representation predates when KeyValue was introduced. We don't have any Avro
support in 0.96 anymore but this would be a good vehicle to put it back. The
representations have limits that were acceptable for a first drop but should be
reworked so large result sets can be chunked/streamed back.
> REST server should publish metrics that are available via HTTP
> ---------------------------------------------------------------
>
> Key: HBASE-7738
> URL: https://issues.apache.org/jira/browse/HBASE-7738
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 0.96.0, 0.94.6
>
> Attachments: 0.94-7738.patch, trunk-7738.patch
>
>
> The REST server should publish metrics that are accessible via HTTP (/metrics
> or /jmx) much like a bunch of the other Hadoop daemons, especially it is a
> Jetty server.
--
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
