Page History

...

 Options we have are:

1. Ignore that problem and:
   1. interpret this value as a real timestamp
   2. or still, interpret −1 as "no timestamp" and other values as a real timestamp (can we borrow 1 millisecond for our needs?).
2. Add a topic property that says if it may have records with "no timestamp'. That case:
   1. users would need to create a new topic and migrate/stream all the records from old topic to the new one
   2. users decide what to do with a record without a timestamp: set the timestamp to current or some specific one based on a message content.
3. Solve this with a new message flag:
   1. add a special boolean flag to message record "hasTimestamp",
   2. write a migration tool that adds this flag to message with the negative timestamp to legacy messages,
   3. make sure clients know about that field and check them
   That makes lookup by timestamp a wired thing: .timeindex will not know about these records.

...