```
┌──┐
│ │
│ processor instance │┐
│ ││
└──┘│
.─.
│
Russ
It sounds like what you have is a case of significant reference data you
need made available to various instances of this processor that knows how
to use that reference state to do its function.
This is similar to cases like IP geo enrichment where the dataset on which
you'd make the
I'm posting this plea for suggestions as I'm short on imagination here.
We have some custom processors that need extraordinary amounts of
configuration of the sort a flow writer would have to copy and paste
in--huge amounts of Yaml, regular expressions, etc. This is what our
flow writers are
Hey Bence and team,
I'd definitely be in favor of a better approach here. When removing
variables, I found myself with the need to update a lot of copies of
nifi.properties as well as other configuration files across many places of
the codebase. I don't know what is the best option/approach here
