All the initial data comes as separate messages with
{"action":"add"
.
which is same or any update so how we can differentiate between Initial dump and update
The idea was that it is responsibility of the information consumer to deal with add/update logic. gobmp is not tracking all bmp sessions from this perspective, as tracking bmp sessions would impact scalability.
whenever I read data from Kafka, I only update messages but not the initial dump and EOR as per https://datatracker.ietf.org/doc/html/rfc7854#section-3.3.
All the initial data comes as separate messages with {"action":"add" . which is same or any update so how we can differentiate between Initial dump and update