[
https://issues.apache.org/jira/browse/NIFI-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174618#comment-16174618
]
Joe Warner edited comment on NIFI-4397 at 9/21/17 11:52 AM:
------------------------------------------------------------
The behaviour I'm seeing now isn't what I remember, so my original description
may not be accurate, but I think the following should illustrate the problem.
I want to be able to set the 'Elasticsearch URL' property dynamically from an
atttribute. Assume I have an attribute set as follows, es_host =
http://<my_es_server>. Then if I set
{quote}
'Elasticsearch URL' = ${es_host}
{quote}
then what I get is
!screenshot-1.png!
I also tried it with es_host = <my_es_server> and 'Elasticsearch URL' =
http://${es_host} and what I get is
!screenshot-2.png!
was (Author: joewarner):
The behaviour I'm seeing now isn't what I remember, so my original description
may not be accurate, but I think the following should illustrate the problem.
I want to be able to set the 'Elasticsearch URL' property dynamically from an
atttribute. Assume I have an attribute set as follows, es_host =
http://<my_es_server>. Then if I set {{'Elasticsearch URL' = ${es_host} }} then
what I get is
!screenshot-1.png!
I also tried it with es_host = <my_es_server> and 'Elasticsearch URL' =
http://${es_host} and what I get is
!screenshot-2.png!
> 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)
