nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Warner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-4396) PutElasticsearchHttp Processor: Type property isn't expanding nifi language expressions
Date Thu, 21 Sep 2017 11:19:00 GMT

    [ https://issues.apache.org/jira/browse/NIFI-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174588#comment-16174588
] 

Joe Warner commented on NIFI-4396:
----------------------------------

Hmmm, seems like it was user error after all. 
Both myself and a colleague had convinced ourselves there was a problem with this - but seems
to be working ok now.

Sorry about that.

> 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)

Mime
View raw message