You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2014/04/22 01:02:15 UTC

[jira] [Created] (HBASE-11048) Support setting custom priority per client RPC

Jesse Yates created HBASE-11048:
-----------------------------------

             Summary: 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
             Fix For: 0.99.0, 0.98.2


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)