Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Although currently we do not enforce any semantic meaning on the Long typed timestamps, we are actually assuming it to be non-negative while storing the timestamp in windowed store. For example, in RocksDBWindowStore we store the timestamp as part of the key, and relying on RocksDB's default lexicographic byte array comparator, and hence negative long value stored in RocksDB will cause the range search ordering to be messed up.
Attachments
Attachments
Issue Links
- links to