I have a disabled inspector connected to a <rejected> port.
When I run it without feature caching enabled the whole fmw runs successfully. When I run it with feature caching enabled it fails:
2019-04-09 11:10:25| 893.2| 0.0|ERROR |PointOnAreaOverlayer_15_<Rejected> (TeeFactory): PointOnAreaOverlayer_7_<Rejected>: Termination Message: 'PointOnAreaOverlayer_7 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''
2019-04-09 11:10:26| 894.7| 1.5|ERROR |PointOnAreaOverlayer_15_<Rejected>: Termination Message: 'PointOnAreaOverlayer_7 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''
2019-04-09 11:10:27| 895.9| 1.2|ERROR |FeatureJoiner (FeatureJoinerFactory): A fatal error has occurred. Check the logfile above for details
2019-04-09 11:10:27| 895.9| 0.0|ERROR |FeatureJoiner (FeatureJoinerFactory): A fatal error has occurred. Check the logfile above for details
The messages point me to change my Rejected Feature Handling to Continue Translation. I'd like to not have to do that for valid reasons, like I might miss a different feature handling error that gets bypassed mistakenly.
So, Is there anyway feature caching can be as tolerant as running the same fmw with non-feature caching with Rejected Feature Handling: Terminate Translation?
Cheers,
Pete
