We have a similar need, and I was thinking about this situation not long
ago because we spent a lot of cycles debugging why our record sets fail (we
handle lots of very low quality data).
I'd like to propose two options here to help debug:
1. Optional feature to add the stacktrace to the
Would it be reasonable to add the details of the failures to the flow file
attributes? I know they exist on the provenance event, but that can not be
persisted easily to file for later analysis and correction. This also seems
harder to locate for non-developers and flow designers.
Thanks,
