UFL Connector NoReplace fuction ( Store Mode)
What we would like is a third option with UPDATE and INSERT, which prevents a new value for the same timestamp from being processed. Such as a NO REPLACE mode.
Kenneth Barber commented
Clint Ramsey commented
I have a question about this:
are we wanting data that is IN order to be tossed, for example, when we get two events in order with the same timestamp? we want the second event to be tossed?
using INSERT mode, if the data is out of order, and matches the timestamp of an existing event, it should get tossed with a -109 showing in the PI DA log