[
https://issues.apache.org/jira/browse/NIFI-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178408#comment-16178408
]
Joseph Percivall commented on NIFI-4397:
----------------------------------------
Hello [~JoeWarner], unfortunately, PutElasticsearchHttp doesn't expose a
FlowFile for evaluating attributes for the URL[1]. It is done this way because
it does the processing in batches (default size of 100) and it would be
essentially random which FlowFile would get picked to evaluate the attributes
for. A ticket is created for it here[2]. For a bit more information, I had
actually created a new one here[3] when I forgot there was already one open.
I'm going to close this ticket since there isn't a problem with the
PutElasticsearchHttp URL field expanding EL.
[1]
https://github.com/apache/nifi/blob/4e4d14f86ff21d2c7d20d9e180acee54a2ddf93b/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L225
[2] https://issues.apache.org/jira/browse/NIFI-1927
[3] https://issues.apache.org/jira/browse/NIFI-4415
> PutElasticsearchHttp Processor: Elasticsearch URL property isn't expanding
> nifi language expressions
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-4397
> URL: https://issues.apache.org/jira/browse/NIFI-4397
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.3.0
> Reporter: Joe Warner
> Priority: Minor
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Despite the documentation saying that the PutElasticsearchHttp processor
> should support expression language this isn't happening. The Index property
> works correctly however. The property validates whether the value looks like
> a URL. But it seems like this validation is taking place before the
> expression is evaluated. Also, expressions like 'http://${url}' still are not
> evaluated.
> Technically I guess this isn't a 'major' issue, but it is quite painful to
> use it without the replacement happening. See also NIFI-4396 which is very
> similar behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
