Incoming records can optionally be filtered by a JMESPath expression added with an additional filter key in a pipeline configuration.
Records which pass through the filter (the filter expression evaluates to true) are processed as normal while records that fail the filter (the filter expression evaluates to false) are dropped. Note that filters can be applied at the topic level and/or the table level. A record needs to pass through all configured filters in order to be loaded to a table.
The filter JMESPath expression must evaluate to a boolean value. Examples of this are JMESPath comparators or functions that return a boolean like contains, starts_with, and ends_with.