Path is defined by the user using a simple syntax with . for subfields and [] for array indexes
As of right now, it looks in all contexts of an event for a value, and if the value is found in at least one context the whole event is accepted by the filter (to be discussed if okay)
Unstruct event filter: unstruct_event_add_to_cart_1.sku==item41 or unstruct_event_add_to_cart==item41
Path is defined by the user using the same syntax
The event name is added by the user as a suffix to unstruct_event_ and validated
If the user does not wish to also validate that the event name is correct, unstruct_event.sku==item41 syntax can be used to skip the validation.
This PR was done by cherry-picking the filters commit on a new branch created from the newly rebased release/1.0.0 branch.
Added the ability for the user to filter events by values inside contexts and unstruct_value.
How to use:
Context filter:
contexts_nl_basjes_yauaa_context_1.test1.test2[0].test3==testValue.for subfields and[]for array indexesUnstruct event filter:
unstruct_event_add_to_cart_1.sku==item41orunstruct_event_add_to_cart==item41unstruct_event_and validatedunstruct_event.sku==item41syntax can be used to skip the validation.This PR was done by cherry-picking the filters commit on a new branch created from the newly rebased release/1.0.0 branch.
Initial PR before rebase: https://github.com/snowplow-devops/stream-replicator/pull/116