[
https://issues.apache.org/jira/browse/HBASE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977550#comment-13977550
]
Andrew Purtell commented on HBASE-11048:
----------------------------------------
bq. I'm not sure how Andrew Purtell feels about your work going into 0.98, so
this issue might be the way forward for that until you finish up the work for
trunk?
Since you asked. Both sound like incremental improvements. We could take one,
then the other. Caveat: Existing public interfaces aren't broken in 0.98,
deprecation is fine. AsyncProcess and MultiServerCallable are package scoped so
those are fine. ClientScanner is Public Stable, but it is just missing one
backwards compatible constructor. Ditto ClientSmallScanner.
> 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.2
>
> 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)
