I do appreciate your point, Tim and Lee. What if I do this instead: append
select attributes to my data payload. Would that minimize the impact on
RAM? Can I do that?
More specifically, my data payload is a string representation of a JSON
object, like so:
{"last":"manson","first":"marilyn"}
and I have an attribute named myKey that contains the value "123abc"
Is there a processor that allows me to wind up with this string
representation of JSON:
{"last":"manson","first":"marilyn", "myKey":"123abc"}
If I could do that, I could avoid loading the entire data payload into an
attribute, and manipulate them in a python script called by ExecuteScript.
I know how to do that, I don't know how to do the above with native
processors.
Thanks in advance for your help.
On Fri, Aug 17, 2018 at 2:02 PM, Lee Laim <[email protected]> wrote:
> Jim,
> I think the ExtractText processor with a large enough MaxCaptureGroup
> length (default :1024) will do that. Though, I share Tim’s concerns
> when you scale up
> Thanks,
> Lee
>
>
> > On Aug 17, 2018, at 11:52 AM, Timothy Tschampel <tim.tschampel@
> vivacehealthsolutions.com> wrote:
> >
> >
> > 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
> >
>
