Selvam, Yes, you can refer to attributes that were added or updated by a previous processor in any follow on component. Just to be clear I understand, the attribute has the *evaluated* value of that expression, or does it contain the literal string you’ve provided below? If it is an expression, you’ll want to use *literal* to evaluate the expression. See the Expression Language Guide [1] for more details.
[1] https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#literal Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Oct 7, 2016, at 1:36 AM, Selvam Raman <[email protected]> wrote: > > Hi, > > can we refer to an attribute from a previous processor for specifying a > boolean clause in routeonattribute processor. > > For Eg. : A flowfile from a previous processor has a attribute called > expression with value ${db.table.name:equals('test')} . Can we refer to this > ${expression} attribute as a boolean clause in routeonattribute processor ? > > -- > Selvam Raman > "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
signature.asc
Description: Message signed with OpenPGP using GPGMail
