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
Not only do the events needs to be tracked, thinking sqlite, we need to figure out if an event has been updated with a new item, thinking may need to hash the events when they come in and if we pull again we can check against the hash to see if it changed.
This will be helpful if using the "LastSeen" field to understand if it is later than the previous "LastSeen"
pull events based on last pull
if eventId is already known
if lastSeen is later than previous lastSeen
Pull new events with all data
If RawId matches existing
Move onto next
else save rawId file
replace old events file with new data
else pull as normal
The text was updated successfully, but these errors were encountered:
Not only do the events needs to be tracked, thinking sqlite, we need to figure out if an event has been updated with a new item, thinking may need to hash the events when they come in and if we pull again we can check against the hash to see if it changed.
This will be helpful if using the "LastSeen" field to understand if it is later than the previous "LastSeen"
pull events based on last pull
if eventId is already known
if lastSeen is later than previous lastSeen
Pull new events with all data
If RawId matches existing
Move onto next
else save rawId file
replace old events file with new data
else pull as normal
The text was updated successfully, but these errors were encountered: