You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Chih Han Yu (Jira)" <ji...@apache.org> on 2019/09/11 16:19:00 UTC

[jira] [Commented] (NIFI-3956) Correct NiFi docs to remove OldestFlowFileFirstPrioritizer as being listed as default prioritizer.

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

Chih Han Yu commented on NIFI-3956:
-----------------------------------

Hi, may I ask has this issue be solved or it's not a issue anymore? 

I still can see OldestFlowFileFirstPrioritizer is default prioritizer on user guide. 

> Correct NiFi docs to remove OldestFlowFileFirstPrioritizer as being listed as default prioritizer.
> --------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-3956
>                 URL: https://issues.apache.org/jira/browse/NIFI-3956
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Documentation &amp; Website
>    Affects Versions: 1.2.0
>            Reporter: Matthew Clarke
>            Priority: Minor
>              Labels: newbie
>
> The embedded NiFi documentation states in two places that the OldestFlowFileFirstPrioritizer is the default prioritizer when nod is selected on a connection.  The actual default behavior is to order the data in such a way as to optimize disk reads. This leads to unexpected behavior for users who believe the oldest FlowFiles will always get processed first.
> It is documented as default in both the "Overview" and User Guide sections of the docs.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)