Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently we assume consistent ordering between serialized and deserialized keys, e.g. if the objects obey objA < objB < objC then the serialized Bytes will also obey bytesA < bytesB < bytesC. This is not true in general of the built-in serdes for signed numerical types (eg Integer, Long). Specifically, it is broken by the negative number representations which are lexicographically greater than (all) positive number representations.
One consequence of this is that an interactive query of a key range with a negative lower bound and positive upper bound (eg keyValueStore.range(-1, 1) will result in "unexpected behavior" depending on the specific store type.
For RocksDB stores with caching disabled, an empty iterator will be returned regardless of whether any records do exist in that range.
For in-memory stores and ANY store with caching enabled, Streams will throw an unchecked exception and crash.