Evan F. created NIFI-12917:
------------------------------
Summary: Content repository claim is being zero'd out
Key: NIFI-12917
URL: https://issues.apache.org/jira/browse/NIFI-12917
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.19.1
Environment: Red Hat 7 running Apache NiFi 1.19.1 with no custom NARs.
Reporter: Evan F.
Attachments: example_MergeContent.txt
I've had rare but consistent instances of MergeContent processors merging files
and losing the content claim/payload while merging. I've pasted an example log
entry below where there's a size to the file pre-merge and the post-merge
content claim becomes zero. I've attached a text file with the configuration of
my MergeContent processor as well. This happens a fraction of a percent of the
time but it happens daily, somewhere around 10 times a day. I scoured forums
and previous tickets but I wasn't able to find a relevant issue. I'm hoping
someone can tell me if this has already been addressed.
INFO [Timer-Driven Process Thread-7] o.a.n.processors.standard.MergeContent
Merge Content[id=e6f460da-018d-1000-1c97-a6bd946d4f61] Merged
[StandardFlowFileRecord[uuid=0e5b7c30-021d-4bd9-9edb-1681c9c14d4e,claim=StandardContentClaim
[resourceClaim=StandardRe sourceClaim[id=1710769372188-3700202,
container=default, section=490], offset=0,
length=52430102],offset=0,name=testFile,size=52430102]] into
StandardFlowFileRecord[uuid=536bf8e4-915b-4dad-9e16-063b35e834c1,claim=,offset=0,
name=testFile.pkg,size=0]. Reason for merging: Maximum number of
entries reached
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
