hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Goltman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-12009) Allow assigning priority to Get, Put, MultiPut, and MultiAction, and passing them the server by the HTable client
Date Wed, 17 Sep 2014 21:26:34 GMT
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)

Mime
View raw message