Every so often using the reverse key scan on the thrift API seems to throw an error We have even isolated to specific record. What is surprising to us is that when we make are start row the very next record before it, it scans correctly. Of course that is not feasible in any means
Thoughts on this -- Abraham Tom Email: [email protected] Phone: 415-515-3621
