Skip to content

Narrow duplicate events detection criteria to avoid skipping new events #6

@ktogias

Description

@ktogias

In case of disaster or other anomaly recovery there may be cases where new events from a channel have id that are previously seen. Matching only id and channel will make listener to skip those events.

We should match events by:
source_id, channel, timestamp and name
in order to detect duplicate events. If any of the above differs then we have a new event that we should add to store.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions