[
https://issues.apache.org/jira/browse/NIFI-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433487#comment-15433487
]
ASF GitHub Bot commented on NIFI-2632:
--------------------------------------
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/919#discussion_r75937909
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/SplitJson.java
---
@@ -61,6 +63,16 @@
+ "Each generated FlowFile is comprised of an element of the
specified array and transferred to relationship 'split,' "
+ "with the original file transferred to the 'original'
relationship. If the specified JsonPath is not found or "
+ "does not evaluate to an array element, the original file is
routed to 'failure' and no files are generated.")
+@WritesAttributes({
+ @WritesAttribute(attribute = "fragment.identifier",
--- End diff --
I don't like the name either, but wanted to keep it consistent with the
other split processors
> Add fragment attributes for SplitJson and SplitXml
> --------------------------------------------------
>
> Key: NIFI-2632
> URL: https://issues.apache.org/jira/browse/NIFI-2632
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> Some "splitting" processors such as SplitText and SplitContent write
> attributes to the split flow files indicating their fragment index, the total
> count, and the filename of the original flow file. This is done to support a
> form of "micro-batching" and/or a split-join pattern in a data flow (i.e.
> split the original file, do work on the individual pieces, and possibly merge
> them together later).
> For consistency and capability, the SplitJson and SplitXml processors should
> write these same attributes for their split flow files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
