<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Best approach to re merging flowfiles in NiFi in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Best-approach-to-re-merging-flowfiles-in-NiFi/m-p/214178#M176093</link>
    <description>&lt;P&gt;MergeContent in Defragment mode would work if you were only merging back one split, so if you have SplitAvro -&amp;gt; ConvertAvroToJson -&amp;gt; ExecuteScript -&amp;gt; MergeContent I think it would work. Once you have multiple SplitAvro processors then each one is writing over the fragment attributes with the most recent split information so MergeContent can only merge back together the most recent Splits.&lt;/P&gt;&lt;P&gt;What are you doing in your ExecuteScript processor to find the problematic record? Just curious to understand that part to see if there is a different way to do the same thing.&lt;/P&gt;</description>
    <pubDate>Fri, 28 Apr 2017 04:13:00 GMT</pubDate>
    <dc:creator>bbende</dc:creator>
    <dc:date>2017-04-28T04:13:00Z</dc:date>
  </channel>
</rss>

