This may not be applicable to your use case depending on message volume / # of attributes; but I would avoid putting payloads into attributes for scalability reasons (especially RAM usage).
> On Aug 17, 2018, at 10:47 AM, James McMahon <[email protected]> wrote: > > I have flowfiles with data payloads that represent small strings of text > (messages consumed from AMQP queues). I want to create an attribute that > holds the entire payload for downstream use. How can I capture the entire > data payload of a flowfile in a new attribute on the flowfile? Thank you in > advance for your help. -Jim
