[
https://issues.apache.org/jira/browse/NIFI-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091215#comment-15091215
]
Joseph Witt commented on NIFI-1346:
-----------------------------------
verified/contrib check all good. +1 . Merged
> Content viewer using old attributes
> -----------------------------------
>
> Key: NIFI-1346
> URL: https://issues.apache.org/jira/browse/NIFI-1346
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Affects Versions: 0.4.1
> Environment: template attached
> Reporter: Joseph Witt
> Assignee: Matt Gilman
> Fix For: 0.5.0
>
> Attachments: 0001-NIFI-1346.patch,
> content_viewer_looks_at_old_attributes (1).xml
>
>
> The attached template allows you to quickly reproduce and observe the problem.
> The flow generates a flow file, replaces the text with a simple two line CSV,
> updates an attribute to add the mime.type of 'text/csv'. For the flow on the
> left if you view provenance events of the 3rd processor (update attribute)
> you will be able to view the content apparently by its auto detected type
> which is considered 'text/plain'. If however you use the flow on the right
> and view the content of provenance events for the fourth processor you'll see
> it is now using the supplied mime.type.
> What I suspect is happening is that the content viewer is being given access
> to the attributes of that flow file as they were before they were changed.
> It should be giving it access to the attributes after the change (at least in
> these cases, i can see when there is a before claim and an after claim that
> it would work differently)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
