Fix Range bug.

This includes some logic to deal with TiKV intrinsics.

Signed-off-by: Ana Hobden <[email protected]>

Author: Hoverbear

src/rpc/tikv/client.rs

@@ -556,7 +556,19 @@ impl KvClient {
         start_key
             .map(|k| req.set_start_key(k.into_inner()))
             .unwrap();
-        end_key.map(|k| req.set_end_key(k.into_inner())).unwrap();
+        end_key
+            .map(|k| {
+                // Scan in TiKV has a weird particularity to it.
+                // The **start** of a scan is inclusive, unless appended with an '\0', then it is exclusive.
+                // The **end** of a scan is exclusive, unless appended with an '\0', then it is inclusive.
+                //
+                // We work around this behavior in this client by making all our scans (Inclusive, Inclusive),
+                // if we have exclusive bounds our own bounds calculation adjusts it.
+                let mut end_key = k.into_inner();
+                end_key.append(&mut vec![0]);
+                req.set_end_key(end_key);
+            })
+            .unwrap();
         req.set_limit(limit);
         req.set_key_only(key_only);