[
https://issues.apache.org/jira/browse/NIFI-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838368#comment-15838368
]
Matt Burgess commented on NIFI-3046:
------------------------------------
As far as I'm aware, the Variable Registry will continue to be exposed to the
user via Expression Language, so at least for the near term I'd recommend
contributing such improvements (and thank you in advance!) and/or writing Jira
cases to document them.
> Use Variable Registry to populate fields that do not currently support EL
> -------------------------------------------------------------------------
>
> Key: NIFI-3046
> URL: https://issues.apache.org/jira/browse/NIFI-3046
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Reporter: Ryan Persaud
> Priority: Minor
>
> My organization has NiFi instances with identical flows running in different
> environments and we would like to take advantage of the ability to substitute
> values from the Variable Registry into processor properties. This works
> great for fields like 'Topic Name' in PutKafka that support Expression
> Language (EL), but it does not work for fields like 'Known Brokers' that do
> not support EL.
> Would it be worth my while to enable EL for these fields and issue a Pull
> Request, or is there another approach in mind for allowing these fields to be
> populated from the Variable Registry? Thanks for the information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
