Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2777
Thanks @markap14 , that is true. My previous comment on the difference
between doc and actual behavior was a false alarm.
I expected that but got different result, so I got confused. But now I
understand what happened in my test. A LookupService was in a child group,
using a RecordReader defined in a parent group. And I set a variable in the
child group. But the RecordReader in the parent group was not able to use it.
Configuring variable at the parent group worked as expected.
- Parent PG
- RecordReader: `Schema Name=${schema.name}`
- Variable registry: `schema.name=parent` (this value can be used)
- Child PG
- LookupService using the RecordReader in the parent PG
- Variable registry: `schema.name=child` (the RecordReader doesn't have
access to variables defined in child PG)
Also, I found that how SchemaAccessStrategy classes caches `PropertyValue`
to evaluate EL at runtime. @MikeThomsen RestLookupService PR #2723 needs to be
updated to follow this pattern when it evaluates EL. I will comment on that PR
for detail.
---
