[
https://issues.apache.org/jira/browse/NIFI-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862802#comment-15862802
]
Matt Burgess edited comment on NIFI-3467 at 2/12/17 2:01 PM:
-------------------------------------------------------------
The Elasticsearch processors support EL in those fields under NIFI-3011 and
NIFI-3095.
I recommend the scheduling improvement be tracked under its own Jira, as it is
a framework issue vs an extensions issue. However I won't split them out yet as
I would like others to weigh in on this list.
was (Author: mattyb149):
The Elasticsearch processors support EL in those fields (except password) under
NIFI-3011 and NIFI-3095. I believe separate work is underway for allowing EL
in sensitive properties such as passwords, but I can't find the Jira case.
I recommend the scheduling improvement be tracked under its own Jira, as it is
a framework issue vs an extensions issue. However I won't split them out yet as
I would like others to weigh in on this list.
> Add EL support to more fields
> -----------------------------
>
> Key: NIFI-3467
> URL: https://issues.apache.org/jira/browse/NIFI-3467
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Tom Schultz
>
> As per conversation with Matt Burgess, here are a list of fields we use that
> don't support EL. We would like to have EL on these fields so we can automate
> the deployment of our NiFis. The list actually turned out to be fairly small,
> so kudos for having EL support on so many.
> * Remote Process Group - Make it configurable in the first place. These
> values will change per deploy
> * GetFile - File filter
> * GetKafka - Zookeeper connection string, topic name, client name, group ID
> * ConsumeKafka - Group ID
> * PutElasticSearch - Cluster name, hosts, username, password
> * All processors - make scheduling configurable (with EL support)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
