Srini, Joe is right that there are perhaps other improvements to your flow. An immediate fix is to remove the parentheses from your regex; .* will still match the entire contents, but as it has no explicit group, you'll save half the heap usage immediately. Is there a reason you are extracting the entire content into an attribute?
Sent from my iPhone > On Mar 7, 2017, at 07:44, Joe Witt <[email protected]> wrote: > > If the value is huge it should certainly be avoided as a flowfile > attribute. The design of nifi allows you to keep the content where it > belongs so that you can obtain high performance and efficient memory > usage throughout the flow on tiny objects as well as huge objects. > Can you talk more about the overall flow so we can suggest better > alternative approaches? > >> On Tue, Mar 7, 2017 at 10:30 AM, srini <[email protected]> wrote: >> Hi Andy, >> Thanks for your reply. This is the regex I used: (.*) >> I want just one attribute, I don't want X.0 and X.1. As the value in the >> attribute is huge,I get OutOfMemory error. So I want to limit to one >> attribute. >> >> Any change I need to make in (.*) to get just one attribute? >> >> thanks >> Srini >> >> >> >> >> -- >> View this message in context: >> http://apache-nifi-developer-list.39713.n7.nabble.com/I-have-attribute-called-X-But-X-0-and-X-1-also-got-created-Why-tp15062p15068.html >> Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
