Re: Common Attributes (FileSize)

Hello Take a look at the example usage of ${fileSize} as shown here [1] It has been this way for quite a while so you should have no problem accessing it using the expression language while configuring the flow. Could you share a template of your flow that is not working? [1]

Re: Common Attributes (FileSize)

I just looked at the data provdence for one of the flow files and it wasn't there. I also tried accessing as ${fileSize} in updateAttribute value. I am using nifi .4.0. Is this attribute added in the newer versions? On 28-Mar-2016 18:50, "Matt Burgess" wrote: > Radhakrishna,

Re: Common Attributes (FileSize)

Radhakrishna, The "fileSize" attribute should be available for every flow file. Can you describe how you are finding the default set of attributes and which ones you are finding? To test, I generated a flow file with the text "Hello" in it, then sent that to a LogAttribute processor, and got the

Re: Having on processor block while another one is running

Vincent This sounds more like an architectural question and even outside of NiFi in order to achieve that especially in the distributed environment one would need some kind of coordination component. And while we can think of variety of way to accomplish that I am not entirely convinced that

Re: Having on processor block while another one is running

I have two processors (that aren't part of the same flow) that write to the same resource (a mongo collection) via a map reduce job. I don't want both to run at the same time. On Mar 28, 2016 6:28 PM, "Joe Witt" wrote: > Vincent, > > Not really and that would largely be by

Re: Having on processor block while another one is running

Vincent, Not really and that would largely be by design. Can you describe the use case more so we can suggest alternatives or perhaps understand the motivation better? Thanks Joe On Mon, Mar 28, 2016 at 4:00 PM, Vincent Russell wrote: > > Is it possible to have one

Having on processor block while another one is running

Is it possible to have one processor block while another specified processor is running (within the onTrigger method). I can do this on a non-clustered nifi with a synchronized block I guess, but i wanted to know if there was a more idiomatic way of doing this. Thanks, Vincent

Re: Flowing from Local NiFi to a Remote HDFS

PutHDFS uses hdfs file system api to copy data to hdfs. There is no requirement that hdfs and NiFi have to be on the same machine. PutHDFS processor asks for the location of the core-site.xml and hdfs-site.xml which inform the file system api’s on where to copy the data to. These config files

Flowing from Local NiFi to a Remote HDFS

If I want to run a local NiFi instance that uses a PutHDFS processor to flow to a remote HDFS...how is this accomplished ? It seems as though the PutHDFS is expecting both a NiFi service and HDFS service running on the same machine ? What if I don't want to run NiFi on my Hadoop cluster ? Thad

Common Attributes (FileSize)

Hi, I am trying extract FileSize attribute from a flowfile. I don't see it in default set of attributes. However, in the documentation it is mentioned https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#common-attributes . Is there any flag that I should enable for me to access

Re: String conversion to Int, float double

Sounds good to me. I presume the processor would still put all attributes in the JSON content, but would use any dynamic properties solely for type coercion? Anything not listed would be treated like a String as it is now (to preserve current behavior). We'd need to document the possible

Re: String conversion to Int, float double

Madhu No i do not believe that it does. I am proposing we make this change so that you can handle this case. Just looking for feedback on whether people like that approach or have a better method. Thanks Joe On Mon, Mar 28, 2016 at 11:36 AM, Madhukar Thota wrote: >

Re: String conversion to Int, float double

Hi Joe, is this dynamic Property works today with AttributesToJSON today? property name: rt_firstbyte property value: Integer -Madhu On Sat, Mar 26, 2016 at 1:13 PM, Joe Witt wrote: > What Madhukar is trying to do seems totally reasonable. As an > alternative to