Hi all, I have been playing with the lookup attribute and noticed a behavior that seems counter intuitive to me:
When using the SimpleCSVLookupService I noticed that whenever the service fails to find a match to a particular value, the LookupAttribute processor still populated the respective dynamic property with "null" and routed the flowfile to match instead of leaving the field untouched and transferring the flow to unmatched. Is this expected behavior? If so, what is the use of unmatched? Kind regards
