[
https://issues.apache.org/jira/browse/HBASE-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474356#comment-13474356
]
Devaraj Das commented on HBASE-6282:
------------------------------------
bq. What do I need to do here Devaraj Das? Enable trace on RPC and I'll see all
the problems above (the pb objects will come out all binary?)
[~stack] Thanks for taking a look at this. Yes, I guess that's what you'd see..
I think most of the changes would be similar to the changes that I did to the
QosFunction as part of HBASE-6414.
bq. How do I see output from 'MonitoredRPCHandlerImpl.toMap()'?
I guess this is used in the UI side. I see toJSON (that internally invokes
toMap) being called from within TaskMonitorTmpl.jamon.
> The introspection, etc. of objects in the RPC has to be handled for PB objects
> ------------------------------------------------------------------------------
>
> Key: HBASE-6282
> URL: https://issues.apache.org/jira/browse/HBASE-6282
> Project: HBase
> Issue Type: Sub-task
> Components: IPC/RPC
> Reporter: Devaraj Das
> Priority: Blocker
> Fix For: 0.96.0
>
>
> The places where the type of objects are inspected need to be updated to take
> into consideration PB types. I have noticed Objects.describeQuantity being
> used, and the private WritableRpcEngine.Server.logResponse method also needs
> updating (in the PB world, all information about operations/tablenames is
> contained in one PB argument).
--
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