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
{{ message }}
This repository has been archived by the owner on Apr 22, 2022. It is now read-only.
Currently an incoming event is always mapped to an Avro record and passed on to the sink. There are situations, however, where it can make sense to discard the event instead of completing the mapping and forwarding a record to the sinks.
Two trivial use-cases which spring to mind include:
Whitelisting domains for which events should be collected.
Suppressing legacy event types.
In addition, once pull request #115 is closed this could serve as a workaround in lieu of issue #6.
The text was updated successfully, but these errors were encountered:
Currently an incoming event is always mapped to an Avro record and passed on to the sink. There are situations, however, where it can make sense to discard the event instead of completing the mapping and forwarding a record to the sinks.
Two trivial use-cases which spring to mind include:
In addition, once pull request #115 is closed this could serve as a workaround in lieu of issue #6.
The text was updated successfully, but these errors were encountered: