[
https://issues.apache.org/jira/browse/NIFI-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156930#comment-15156930
]
Joseph Witt commented on NIFI-1544:
-----------------------------------
Hello Shekhar. I will verify and provide a template in a moment but it is
important that in merge content you set the correlation attribute to '${date}'
if you want it to use the value of date you are looking for. This should
definitely work the way you want it to. Further, notice in MergeContent there
is a property which lets you control the resulting attributes. All attributes
that match across all flowfiles merged should end up on the resulting flow
file. So, if the date attribute isn't there that is telling us that the value
of date did not match which means correlation isnt' happening as you would like.
Will put up a template that shows how this should work in a sec (hopefully)
> [MergeContent Processor] Correlation Attribute should be available to next
> processor
> ------------------------------------------------------------------------------------
>
> Key: NIFI-1544
> URL: https://issues.apache.org/jira/browse/NIFI-1544
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.4.1
> Environment: unix, nifi-0.4.1 compiled with hadoop-2.4.0
> Reporter: Shekhar Bansal
> Priority: Minor
>
> My workflow:
> ListFiles
> FetchFIles
> SplitFIles
> ExtractText - Extract "date" from records
> MergeContent - Correlation Attribute=date
> UpdateAttribute - outputDirecoty=/data/output/${date}
> PutFile
> Problem is date is not available in UpdateAttribute processor.
> Since all the records in a particular flow have same date, it should be
> available in UpdateAttribute processor.
> Because of this issue I have to read merged flow again(only first record).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
