Re: GetHTTP processor error

I think you're thinking about it the wrong way. You aren't actually using any attributes (attributes are on flowfiles, properties on processors), just utilizing the functions of expression language. So you can manually put in everything you would normally as a literal then reference the

Re: GetHTTP processor error

Hi Joe, Another quick question. How can I encode some part of the URL? Like in example bellow after searchpattern= space between Matt Dupe needs to be encoded.

Re: GetHTTP processor error

Hello Igor, The URL property for GetHTTP supports expression language. Check out this function: https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#urlencode Hope that helps, Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On

Re: GetHTTP processor error

Guys, I think I get it. Is this how it should be? http://api.twingly.com/analytics/Analytics.ashx?key=75744154-6ACB-3340-937A-9B5A59FA8F30=${literal('Matt Dupe'):urlEncode()}=2=${now():minus(60):format("-MM-dd HH:mm:ss")}=${now():format("-MM-dd HH:mm:ss")} On Tue, Dec 15, 2015 at

Re: GetHTTP processor error

But how I define attribute "url" in GetHTTP processor? I tried to ad a property and got an error that property not defined or supported. On Tue, Dec 15, 2015 at 4:57 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Hello Igor, > > The URL property for GetHTTP supports expression

Re: GetHTTP processor error

That would be nice addition. On Tue, Dec 15, 2015 at 5:46 PM, Mark Payne wrote: > That looks about right to me. But that seems a little bit painful. Perhaps > we can make that easier by offering a new Property that allows you to just > tell the Processor that it needs to

Re: GetHTTP processor not working

Thanks Joe .!! With the modified URL it worked. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/GetHTTP-processor-not-working-tp5711p5790.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Facing Issue while connecting with HDFS

Hello, By default NiFi will interact with HDFS as the user that started the NiFi process. If you can only access HDFS as the superuser then you will probably need to start NiFi as that user. There is a "run.as" property in conf/bootstrap.conf where you can specify a username to run NiFi as, but

Re: How to iterate through complex JSON objects.

As an alternative approach, could you use SplitJSON first to split on the items array? You would get a FlowFile for each item, then when you use EvaluateJSONPath you would be dealing with only a single FlowFile so you could extract the id and title and use ReplaceText like you were already doing.

Re: How to iterate through complex JSON objects.

Thanks Bryan!! Infact I followed the exact approach that you told. Just that I was clueless about using Mergecontent processor. So I wrote my custom script to combine the different outputs and executed it using Execute Stream command. Will try the same with Mergecontent. -- View this message in