Mule Batch FilterBy – Ankush Sharma

What is Mule Batch Filter?

You can apply one or more filters as attributes to any number of batch steps within your batch job. By having batch steps accept only some records for processing, you streamline processing so that Mule focuses only on the data which is relevant for a particular batch step.

Filters are applied within batch steps. Use an Accept Expression to process only those records which, relative to the MEL expression, evaluate to true; if the record evaluates to false, the batch step does not process the record. In other words, those records with a filter expression that resolves to false are the ones Mule filters out.

Prerequisites for Mule Batch Filter

The user must be familiar with Anypoint Studio. Know basics of Batch Processing. understand how batch jobs handle records which fail processing. 

Mule Batch Filter – Configuration Wizard (General Tab)

Following are the options on batch filter – Name – The name of the batch filter component. Accept Expression – Expression that will be evaluated for acceptance. Accept Policy – This tells what results to accept or discard.

Mule Batch Filter – Configuration Wizard (Notes Tab)

This tab is used to add special notes for Mule Batch Filter component.

Mule batch component characteristics

Batch filters only apply to batch steps which, in turn, are only usable within the batch process phase of a batch job. You cannot apply filters with the Input or On Complete phases.

If you apply no filters to a batch step, the batch processes only those records which succeeded processing in all preceding steps. In other words, the default Accept Policy applied to all batch steps is NO_FAILURES.

When a batch job instance exceeds its max-failed-records value, regardless of the filter set on the batch step, the step does not process any records, and simply pushes the failed batch job instance to the On Complete phase. Read more about failure handling in batch jobs.

Thank You!