[
https://issues.apache.org/jira/browse/NIFI-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303826#comment-17303826
]
ASF subversion and git services commented on NIFI-8337:
-------------------------------------------------------
Commit d610b1ccea4ec4282d10aa9d3f65ed6f3d263f95 in nifi's branch
refs/heads/support/nifi-1.13 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d610b1c ]
NIFI-8337: This closes #4910. Fixed bug in StandardProcessSession where the
session didn't account for FlowFile's contentClaimOffset when seeking to the
appropriate location in the stream.
Signed-off-by: Joe Witt <[email protected]>
> When reading FlowFile content, processor can start at wrong offset
> ------------------------------------------------------------------
>
> Key: NIFI-8337
> URL: https://issues.apache.org/jira/browse/NIFI-8337
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.1
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.14.0, 1.13.2
>
> Attachments: NiFi_Flow.json
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Will attach a flow that replicates this issue.
> With the given flow, the data that is routed from ConvertRecord should
> contain two FlowFile whose contents are:
> {code:java}
> { "a" : "a" } {code}
> and
> {code:java}
> { "a" : "b" } {code}
> However, the result is that both FlowFiles have content:
> {code:java}
> { "a" : "a" } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
