they failed and fix them manually.
This leads me to https://issues.apache.org/jira/browse/NIFI-3351. I think I
need a way to store failed flowfiles, fix them and reprocess them. The process
group I am currently considering implementing everywhere is:
Input Port [Failed Flowfile] --> PutS3 deadletter///${
No confusion, Nick. I hear you. In our case...
We attempt to reroute flowfile back through processors that, for
whatever reason, might bring them to a state in which they can be
successful (much to explain there, but...) and others we route to a
similar, "deadletter" store w
m
> manually.
>
> This leads me to https://issues.apache.org/jira/browse/NIFI-3351. I think
> I need a way to store failed flowfiles, fix them and reprocess them. The
> process group I am currently considering implementing everywhere is:
>
> Input Port [Failed Flowfile] -
failed flowfiles, fix them and reprocess them. The process
group I am currently considering implementing everywhere is:
Input Port [Failed Flowfile] --> PutS3 deadletter///${uuid} --> PutSlack
ListS3 deadletter/// --> FetchS3 -> Output
Port [Fixed]
This gives me storage of failed mes
ink I
need a way to store failed flowfiles, fix them and reprocess them. The
process group I am currently considering implementing everywhere is:
Input Port [Failed Flowfile] --> PutS3 deadletter///${uuid} --> PutSlack
ListS3 deadletter/// --> FetchS3 ->
Output Port [Fixed]
This gives me
