[
https://issues.apache.org/jira/browse/HBASE-26531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502367#comment-17502367
]
Nick Dimiduk commented on HBASE-26531:
--------------------------------------
[~zhangduo] [~taklwu] [~elserj]
I spent some time on this. I have a test that verifies that our coprocessor
exec calls are traced as {{hbase.pb.ClientService/ExecService}}. However, I
don't think we expose enough metadata in our API to know at runtime what
user-provided protobuf service is being executed. Our system of generics and
callbacks is elegant, but strips a lot of detail from the runtime types. If I
modify the IA.Public interface a little, we access the fully qualified service
name. However, I don't see a way to retrieve the name of the service method
from the {{ServiceCaller}}. Maybe with some byte code investigation of the
content of the callable?
> Trace coprocessor exec endpoints
> --------------------------------
>
> Key: HBASE-26531
> URL: https://issues.apache.org/jira/browse/HBASE-26531
> Project: HBase
> Issue Type: Sub-task
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> Decide how to trace Coprocessor Exec endpoints. They either look like table
> operations OR generic RPC calls... I'm guessing the latter, but will give it
> some study.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
