RE: Expression Language

["Jones, Patrick L." <pl...@mitre.org>]

Thank you Bryan.  I did need to use the variable registry support.  That fix the problem.

From: Bryan Bende <bb...@gmail.com>
Sent: Wednesday, October 31, 2018 4:52 PM
To: users@nifi.apache.org
Subject: Re: Expression Language

You haven't said which processor/service you are using, but you may want to check the docs for that component to see whether it supports expression language from flow file attributes, some only support variable registry.

Most of the elastic search processors look like the host only supports variable registry [1].

[1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-nar/1.8.0/org.apache.nifi.processors.elasticsearch.PutElasticsearch/index.html


On Wed, Oct 31, 2018 at 4:44 PM Boris Tyukin <bo...@boristyukin.com>> wrote:
looks right to me...Did you check flowFile attributes in provenance events to make sure your attributes are populated? also check exact spelling and casing. If still does not work, show us some screenshots of your flow and properties
Boris

On Wed, Oct 31, 2018 at 4:04 PM Jones, Patrick L. <pl...@mitre.org>> wrote:
Howdy,

         I’m having trouble with the expression language.  I have 2 attributes ElasticIP and ElasticPort.  I’m trying to use them in an Elastic URL.  If I hard code the values in it works find.  If I use the attributes I get a null pointer.  I have tried various variations on:
http://${ElasticIP}:${ElasticPort}<http://$%7bElasticIP%7d:$%7bElasticPort%7d>

where ElasticIP = 10.0.0.0 and ElasitPort is 9200

Any thoughts on what the expression should be?

Thank you