[
https://issues.apache.org/jira/browse/NIFI-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080301#comment-18080301
]
ASF subversion and git services commented on NIFI-15916:
--------------------------------------------------------
Commit 2847bb87e423bbb03f28309c56f36e641ee56dae in nifi's branch
refs/heads/main from Alaksiej Ščarbaty
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2847bb87e42 ]
NIFI-15916 Log dropped FlowFiles when content is missing (#11221)
In handleContentNotFound both branches threw MissingFlowFileException
with the same generic "Unable to find content for FlowFile" message,
giving operators no FlowFile identity and no way to distinguish an
unrecoverable drop from a recoverable rollback.
Registered-claim branch (markForAbort + drop): enrich the exception
message with the FlowFile identity and emit a WARN log so the drop is
recorded even if the caller swallows the exception.
Transient-claim branch (rollback returns the FlowFile to its queue):
enrich the message only - name the in-flight content and signal the
session is rolling back so callers can tell this is recoverable.
> Log any dropped FlowFiles when content is missing
> -------------------------------------------------
>
> Key: NIFI-15916
> URL: https://issues.apache.org/jira/browse/NIFI-15916
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When a FlowFile is dropped due to missing content, its details are not
> recorded.
> `MissingFlowFileException` message should contain FlowFile uuid and an
> explicit statement the FlowFile is being dropped.
> In addition it would be helpful to mention FlowFile drop in a log, in case a
> thrown `MissingFlowFileException` is not printed by a caller.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
