Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
0.89-fb
-
None
Description
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.