compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
# Open question: what is the input to the range? A pair of bytestrings and the inclusion flags seem reasonable.
# Are we comfortable with the "and keep it open" behavior of the range query response?
# (Michael): How are we dealing with that on the client side? Because technically its a single get, but this would span multiple vbuckets and nodes. Who does the gathering and aggregation of the results? I guess its nearly impossible to determine all nodes in a range for a given key? Or ask all of them and merge them on the client?

h1.{anchor:h.2kpu6sl12tai}{*}Changelog*
Updated to indicate release is post 3.0 on 2014-03-11. This was always intended before publication, but it wasn't changed.
{anchor:_GoBack}
Added question on 2014-03-26 by Michael.