[jira] [Commented] (NIFI-334) When WriteAheadFlowFileRepo is restoring FlowFiles, it needs to look at the swapped flow files, Id's before setting the max id for the FlowFile ID.

["Mark Payne (JIRA)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-334:
---------------------------------

The notion of a FlowFile's ID was created long ago and its use really has faded away in favor of just using the "uuid" attribute. This is a bug that has existed for a long time, but it doesn't really cause any significant side effects, unless a Processor depends on this being unique (none of them in the current build use this except for logging purposes). The only place that I can see this being used with any significance is the Mock Framework. Rather than fixing this, I am tempted instead to mark the getId() method as deprecated, describe in the JavaDocs that it is not a reliable method for determining uniqueness, and just remove it all together in 1.0.0

> When WriteAheadFlowFileRepo is restoring FlowFiles, it needs to look at the swapped flow files, Id's before setting the max id for the FlowFile ID.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-334
>                 URL: https://issues.apache.org/jira/browse/NIFI-334
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Daniel Ueberfluss
>            Assignee: Mark Payne
>            Priority: Minor
>             Fix For: 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)