nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (NIFI-7469) Processors that write zero-byte content may cause Content Repository Cleanup to fail
Date Fri, 10 Jul 2020 14:46:00 GMT


ASF subversion and git services commented on NIFI-7469:

Commit 1fc25db47cdecef404548ac011de2c2564574932 in nifi's branch refs/heads/main from Mark
[;h=1fc25db ]

NIFI-7469: Updated RepositoryRecord to include flag indicating whether or not the content
of a FlowFile was modified. This allows us to explicitly keep track of this state rather than
implying it (potentially incorrectly).

This closes #4399.

> Processors that write zero-byte content may cause Content Repository Cleanup to fail
> ------------------------------------------------------------------------------------
>                 Key: NIFI-7469
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.10.0, 1.11.0, 1.11.1, 1.11.4
>         Environment: Windows 10, ubuntu 18.04
>            Reporter: Stefano Piana
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 1.12.0
>         Attachments: ReplaceTextBug.xml
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Trying to replace an empty flowfile with and empty value may cause the content repository 
> to accumulate and not being correctly cleaned up until the next NiFi restart.
> this behaviour has been observed on nifi 1.10+
> to reproduce the problem just generate a flowfile that has some content, then replace
the content with the ReplaceText processor setting it to always replace and set the replacement
to empty string. Copy the ReplaceText processor and try replacing the content with an empty
string again, then just use any processor to drain the flowfiles. This will cause the content
repository to accumulate and stop being correctly cleaned up.
> here attached a simple flow that reproduces the problem.

This message was sent by Atlassian Jira

View raw message