You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Alex Goltman (JIRA)" <ji...@apache.org> on 2014/09/17 23:26:34 UTC

[jira] [Created] (HBASE-12009) Allow assigning priority to Get, Put, MultiPut, and MultiAction, and passing them the server by the HTable client

Alex Goltman created HBASE-12009:
------------------------------------

             Summary: Allow assigning priority to Get, Put, MultiPut, and MultiAction, and passing them the server by the HTable client
                 Key: HBASE-12009
                 URL: https://issues.apache.org/jira/browse/HBASE-12009
             Project: HBase
          Issue Type: New Feature
          Components: Client, regionserver
    Affects Versions: 0.89-fb
            Reporter: Alex Goltman
             Fix For: 0.89-fb


Allow assigning priority to Get, Put, MultiPut, and MultiAction, in preparation for later QoS tasks.
Current policy regarding MultiPuts and MultiAction sent by client after batching operations - the Multi operation's priority will be equal to the one of the contained operations' priority. If the client would like to send mixed Puts/Gets with different priorities he should call flushCommits() in between. The logic behind this is the server will have to process all the operations in the batch operation, and thus they all must have the same priority.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)