[
https://issues.apache.org/jira/browse/NIFI-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064171#comment-15064171
]
Mark Payne commented on NIFI-1307:
----------------------------------
Actually, now I am remembering that there are two reasons that we deprecated it
- NIFI-334 was also a bug that indicated that getId() was not always unique, as
it could potentially be duplicated on restart (though unlikely, it is
possible). So we should leave this deprecated for now.
A better strategy may be to use a time-based UUID for the flowfiles, which
would provide us with the same general idea here. For the mean-time, we will
leave this deprecated and simply use the deprecated method for 1279, as the bug
described here will - at worst - result in the solution provided for NIFI-1279
to be only as effective as it is currently (before the 1279 patch is applied).
> Un-deprecate FlowFile.getId()
> -----------------------------
>
> Key: NIFI-1307
> URL: https://issues.apache.org/jira/browse/NIFI-1307
> Project: Apache NiFi
> Issue Type: Task
> Components: Core Framework
> Reporter: Mark Payne
> Fix For: 0.4.1
>
>
> In 0.4.0, we deprecated the getId() method of FlowFile because it was no
> longer being used in any substantive way. However, we have found a bug in
> same of the Prioritizers (address in NIFI-1279) that is being addressed by
> using this method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
