You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can get the same event twice if the database stores an event and the queryParams includes it. The first call could call realTimeEventService.getEvents(), allocating a real time buffer. The next call to get events could get the events from the dao. The third next call could get the same event from the real time queue since the buffer is allocated.
To fix, we should have a parameter to explicity say whether we want real time or historical events?
The text was updated successfully, but these errors were encountered:
Reviewed the code - I think this is a bug, but we need a test.
The logic for getting real time events is:
We can get the same event twice if the database stores an event and the queryParams includes it. The first call could call realTimeEventService.getEvents(), allocating a real time buffer. The next call to get events could get the events from the dao. The third next call could get the same event from the real time queue since the buffer is allocated.
To fix, we should have a parameter to explicity say whether we want real time or historical events?
The text was updated successfully, but these errors were encountered: