[
https://issues.apache.org/jira/browse/HBASE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987229#comment-13987229
]
Jesse Yates commented on HBASE-11048:
-------------------------------------
Yeah, I got sidetracked by internal work and then it proved a bit more effort
than in trunk. Specifically, the ProtobufUtil is used all over the place,
rather than using the PayloadCarryingRpcController directly in HTable. Which
means adding a lot of methods for backward compatibility and a lot places where
it would be easy to miss using the controller.
Open question: should we support a custom controller factory for:
* coprocessors
* admin functions
* master calls
* internal system table look ups (e.g. determining target region in HConnection)
My gut says yes, no, no, no, respectively. Any thoughts?
> Support setting custom priority per client RPC
> ----------------------------------------------
>
> Key: HBASE-11048
> URL: https://issues.apache.org/jira/browse/HBASE-11048
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 0.99.0, 0.98.2
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Labels: Phoenix
> Fix For: 0.99.0, 0.98.3
>
> Attachments: hbase-11048-trunk-v0.patch
>
>
> Servers have the ability to handle custom rpc priority levels, but currently
> we are only using it to differentiate META/ROOT updates from replication and
> other 'priority' updates (as specified by annotation tags per RS method).
> However, some clients need the ability to create custom handlers (e.g.
> PHOENIX-938) which can really only be cleanly tied together to requests by
> the request priority. The disconnect is in that there is no way for the
> client to overwrite the priority per table - the PayloadCarryingRpcController
> will always just set priority per ROOT/META and otherwise just use the
> generic priority.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
