Github user PrashanthVenkatesan commented on the issue:
https://github.com/apache/nifi/pull/2820
@ottobackwards Thanks for your valuable review.
I thought if user flow sends this json to some sink (say kafka), it would
be good to have the raw_data with it. are you suggesting me to remove this ? ..
Providing template also for the above purpose, if the external system wants
to parse the raw or understand the parsing configs, template would be
necessary. Also further ahead if we support other netflow related protocols
that has concept of dynamic templates, it is worth sending templates via
relationship.
I understand your point adding raw to json looks like conflating, but i
felt creating the another relationship would create separate content claim for
each record that might degrade the throughput of processor.
would like to know your view on my points..
I will incorporate all the other review comments and soon push the commit.
---
