You have to do this in two subsequent UpdateAttribute instances because the order of attribute definition (within an instance) is not deterministic. We have gotten a lot of questions about this, so perhaps it makes sense to investigate as a new feature. However, if that decision is made, I think substantial changes to the interface would need to be made to allow for manual reordering of property descriptors, which is not currently supported, and the transmission of that data via the DTOs in the API would need to be changed as well, because JSON keys are not ordered.
Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On May 16, 2019, at 2:08 PM, Boris Tyukin <[email protected]> wrote: > > Hi guys, > > is it possible to reuse just defined attribute in another attribute in the > same instance of UpdateAttribute processor or I really have to use two > separate UpdateAttribute processors? > > For example, I define name=boris and then I want to add another attribute > greetings=Hi ${name} > > If I do it in NiFi 1.9, greetings attribute is set to "Hi "
