[
https://issues.apache.org/jira/browse/NIFI-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174167#comment-16174167
]
Joseph Percivall commented on NIFI-4397:
----------------------------------------
Hello [~JoeWarner], similar to my comment on NIFI-4396, can you elaborate a bit
on what you mean by "expanding" the Nifi expressions and why you believe it's
not working?
Your comment "validation is taking place before the expression is evaluated" is
correct and done on purpose. Validation of the properties is done after the
processor configuration is saved and prior to running the processor. If
expression language (EL) is present in a property then we can't fully validate
it since a property may be reliant on an incoming FlowFiles' attributes or some
other transient aspect to be evaluated. So for validation, we typically will
first check if it contains EL, if so then mark it as valid. If it does not then
continue on with proper validation.
> 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
>
> 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)
