ClientID field looks different when the same event is included in the PlaybackQueryResponse coming from the chrono-player's activeDataStore compared to when this same event is included in PlaybackQueryResponse to the later query and is coming from the archived HDF5
I suspect that the recent change in ClientId ( release 2.7 or 2.8) was not propagated tto the HDF5 archive writing and reading modules
How to reproduce:
- bring up the chronolog system locally using chrono-keepr with dual-endpoint extractor
- use chronolog-client-writer. to records a bunch of events
- use chronolog-cleint-reader to query events within the chrono-player's access window ( default is 5 mins ); the events would be coming from the player's active DataStore
- use chronolog-cleint-reader to query events after the chrono-player's access window ( default is 5 mins ) have passed. the same events would be coming from the archived hdf5 files
ClientID field looks different when the same event is included in the PlaybackQueryResponse coming from the chrono-player's activeDataStore compared to when this same event is included in PlaybackQueryResponse to the later query and is coming from the archived HDF5
I suspect that the recent change in ClientId ( release 2.7 or 2.8) was not propagated tto the HDF5 archive writing and reading modules
How to reproduce: