d_hscan does not work when compression strategy is set to something other than NONE

seems like `d_hscan` has a bug when using `CompressionValueOperation` `ScanResult` gets a stale cursor and therefore does not scan all the records. It should get a cursor from the result of the `client.hscan(key, cursor).getResult()` execution. The result of this is that not all records are returned when compression strategy is set to `THRESHOLD`