Hello Eric,
Have you found any solution for this?
If your trailers (footer?) starts with certain byte sequence, then
SplitContent may be helpful to split the content into Header+Payload,
and the Trailers.
If that works, then the subsequent flow can do something creative
probably using
Chad,
I wanted to echo Bryan and say thanks for sharing the details of an
upgrade process that works. Until we have improved NiFi to handle the
upgrades regardless of order of steps, this is a helpful reference for
the community for a sequence that can work.
Cheers,
Kevin
On Tue, Mar 19, 2019
Chad,
Thanks for reporting your experience and glad to hear that there is a
good process to follow.
We do want to make this situation better and there is a JIRA to track
the issue [1].
Thanks,
Bryan
[1] https://issues.apache.org/jira/browse/NIFI-6028
On Tue, Mar 19, 2019 at 11:23 AM Chad
Hey guys,
I'm going to be upgrading my NiFi clusters to 1.9.1 soon so this topic was
important to me. I've done some testing and wanted to share my results.
*Test environment setup*:
2 NiFi Clusters
1 NiFi Registry
Dev NiFi on 1.8.0 versioning flows with NiFi Registry 0.2.0
Cert NiFi on 1.8.0
Hi Eric,
I did some quick tests, replaceRegex works well for me. The regex patterns
should behave as expected (see:
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/functions/ReplaceRegex.java#L49-L49),
I don't see any reason why
