[
https://issues.apache.org/jira/browse/NIFI-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202896#comment-15202896
]
Mark Payne commented on NIFI-1650:
----------------------------------
Looking into this more, I now see that the issue does NOT affect the Provenance
Events. When viewing content from a Provenance Event, a new Content Claim is
generated, which does take into account the offset. So we don't need to skip to
any particular location in the stream, since the stream provided by the Content
Repository already is in the correct location.
The existing patch, I believe, is good as-is.
> When listing queue content it appears the wrong content claim is being used
> ---------------------------------------------------------------------------
>
> Key: NIFI-1650
> URL: https://issues.apache.org/jira/browse/NIFI-1650
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Reporter: Joseph Witt
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 0.6.0
>
> Attachments:
> 0001-NIFI-1650-Ensure-that-we-seek-to-the-appropriate-off.patch,
> View_Content_using_wrong_content_claim.xml
>
>
> Will attach template to reproduce. Noticed this will testing the patches for
> NIFI-1634. The flow runs and 11 outputs are produced on the queue. If you
> do the queue listing you can try to view content but it sees the full object
> size of the original claim it appears so it shows the full object. It shows
> the proper size on the attributes but then when going to view content it sees
> the original/too large size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
