When making use of the Field Mapper stage to generate a new child field path within a record, if the syntax of that child field path is invalid it generates a stage-level exception which fails the entire pipeline.
Instead, it should generate a record-level exception and handle the record via the pipeline's configured "Error Record Handling".
For example, if a Field Mapper is preceded by a parsing stage (Jython eval, Grok parser, etc.) which generates a value like:
The Field Mapper stage throws a "java.lang.IllegalArgumentException: Invalid fieldPath" stage exception, which fails the entire pipeline. Instead, it should pass this particular record through to the error record handler and allow the pipeline to continue processing.