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

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

Commit 2465f67dfe4132b3a52c14a7c0bb9cbdf21e507c in nifi's branch 
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2465f67 ]

NIFI-6339: Only call @OnConfigurationRestored method on components when they 
are created if FlowController has been initialized

This closes #3530.

Signed-off-by: Bryan Bende <bbe...@apache.org>


> ListHDFS processor will list files without using previous state when cluster 
> startup
> ------------------------------------------------------------------------------------
>
>                 Key: NIFI-6339
>                 URL: https://issues.apache.org/jira/browse/NIFI-6339
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.9.0, 1.9.1, 1.9.2
>            Reporter: Hsin-Ying Lee
>            Priority: Major
>         Attachments: NIFI-6339.v0.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When the node startup, NiFi will create processor and load the property & 
> state.
> But ListHDFS will ignore the previous listed-state stored on Zookeeper, and 
> relist all file again.
>  
> And I found when we call the function setProperty, we only check the value 
> between default and newValue. If oldValue is same with newValue, it'll also 
> trigger function onPropertyModified.
> It casue ListHDFS loaclVariable: resetState to be true. When ListHDFS be 
> triggered, it'll clear the state empty, and relist all the files in the 
> directory.
>  
> {code:java}
> // AbstractComponentNode.java
> if (!value.equals(propertyModComparisonValue)) {
>     try {
>         onPropertyModified(descriptor, oldValue, value);
>     } catch (final Exception e) {
>         // nothing really to do here...
>     }
> }
> {code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to