[jira] [Commented] (NIFI-4422) QueryElasticsearchHttp: Expression Language not being evaluated for Query property

["Matt Burgess (JIRA)" <ji...@apache.org>]

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

Matt Burgess commented on NIFI-4422:
------------------------------------

[~JoeWarner] I can't reproduce this issue with QueryElasticsearchHttp. According to the code, the unit tests, and my tests, the Query parameter has always supported Expression Language and has always evaluated it against the incoming flow file (if it exists). Is this still an issue for you?

> QueryElasticsearchHttp: Expression Language not being evaluated for Query property
> ----------------------------------------------------------------------------------
>
>                 Key: NIFI-4422
>                 URL: https://issues.apache.org/jira/browse/NIFI-4422
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.3.0
>            Reporter: Joe Warner
>            Priority: Minor
>
> I fear this is related to [#NIFI-4397] and thus [#NIFI-1927] (in which case there may be no help for me) but I am struggling with expansion of the Query property. If I put my Lucene query (_type:time AND user_id.id[800000 TO 1150000]) directly into the Query property then everything seems to work fine. But if I set an attribute _query with this value and then set the Query property to ${_query} then it doesn't work and the processor seems to fail rather silently. I can't see anything in the logs that suggests to me that was an error.
> Is this just another case of when it says "Supports Expression Language: true" in the documentation that this only really tells a small part of the story?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)