[ 
https://issues.apache.org/jira/browse/NIFI-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272863#comment-16272863
 ] 

ASF subversion and git services commented on NIFI-4606:
-------------------------------------------------------

Commit 45df23b1e09f340fb2c7f3c3234462570ddb5f6b in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=45df23b ]

NIFI-4607, NIFI-3975, NIFI-4602, NIFI-4606: This closes #2272. Fixed bug in 
TailFile that caused new Primary Node to not pull current Clustered State when 
File Location was set to Remote. Fixed bug that caused TailFile to occasionally 
become 'stuck' when the file it is tailing is renamed and a new file is created 
with the same name. Removed the 'Rolling Strategy' property from TailFile 
because it is not actually used in the processor anymore. Deleted 
MonitorMemoryTest because the unit test was testing the behavior of 
FlowController more than the behavior of the reporting task itself and in order 
to do so had a dependency in the pom.xml on nifi-framework-core, which means 
that it no longer compiles when FlowController is modified.

Signed-off-by: joewitt <joew...@apache.org>


> TailFile has a property named "Rolling Strategy" but it is never used
> ---------------------------------------------------------------------
>
>                 Key: NIFI-4606
>                 URL: https://issues.apache.org/jira/browse/NIFI-4606
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 1.5.0
>
>
> The TailFile processor has a property that is named "Rolling Strategy." It 
> has two allowable values "Fixed name" or "Changing name." I was unable to 
> understand from the documentation what the intent of the property was, so I 
> began to read the code in order to understand so that I could better update 
> the documentation. However, looking through the code, I found that the 
> property was only ever looked at in the customValidate method and never used 
> for any logic within the processor.
> Therefore, this property needs to be removed from the processor, since it 
> adds complexity to the processor's configuration and doesn't actually affect 
> the behavior of the processor itself.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to