THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Options we have are:
- Ignore that problem and:
- interpret this value as a real timestamp
- or still, interpret −1 as "no timestamp" and other values as a real timestamp (can we borrow 1 millisecond for our needs?).
- Add a topic property that says if it may have records with "no timestamp'. That case:
- users would need to create a new topic and migrate/stream all the records from old topic to the new one
- 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.
- Solve this with a new message flag:
- add a special boolean flag to message record "
hasTimestamp
", - write a migration tool that adds this flag to message with the negative timestamp to legacy messages,
- make sure clients know about that field and check them
.timeindex
will not know about these records. - add a special boolean flag to message record "
...