Toivo, You shouldn't feel overly constrained here either. If you receive an object that has four parts within it and you want to do four different types of analysis of those parts in parallel a valid play is to have a processor which understands that and behaves that way. That might be more appropriate given the specific nature of the use case. Obviously the more niceties off the shelve NiFi can provide the better. As you think through this more feel free to keep throwing out what you're thinking and seeing we can try to help. This feels like the beginning of a blog post or wiki page ...
Thanks Joe On Thu, Jun 18, 2015 at 8:17 AM, Toivo Adams <toivo.ad...@gmail.com> wrote: > Mark, > Make perfect sense. > > I don’t have much JSON experience, so I might be wrong. > But Avro serialization/deserialization should much faster than JSON? > > Maybe I’ll create some structured data holder - MultipartContent > and custom MergeContent which is capable of merging MultipartContent’s. > > Thanks > Toivo > > > > > -- > View this message in context: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/How-to-implement-Scatter-Gather-tp1944p1949.html > Sent from the Apache NiFi (incubating) Developer List mailing list archive at > Nabble.com.
