You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2017/09/21 02:47:00 UTC
[jira] [Commented] (NIFI-4396) PutElasticsearchHttp Processor: Type
property isn't expanding nifi language expressions
[ https://issues.apache.org/jira/browse/NIFI-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174156#comment-16174156 ]
Joseph Percivall commented on NIFI-4396:
----------------------------------------
Hello [~JoeWarner], can you elaborate a bit on what you mean by "expanding" the Nifi expressions and why you believe it's not working?
Looking at the source for PutElasticsearchHttp 1.3.0, we do the call to evaluate the type here[1], the property supports expression language (as stated here[2]) and the validator handles it here[3].
[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#L244
[2] 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#L106
[3] https://github.com/apache/nifi/blob/4e4d14f86ff21d2c7d20d9e180acee54a2ddf93b/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/processor/util/StandardValidators.java#L170
> PutElasticsearchHttp Processor: Type property isn't expanding nifi language expressions
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-4396
> URL: https://issues.apache.org/jira/browse/NIFI-4396
> 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. Looking the source I notice that these two properties use different validators and wonder if the issue could be related.
> Technically I guess this isn't a 'major' issue, but it is quite painful to use it without the replacement happening.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)