Re: TestRunner fileSize Attribute

2019-02-26 Thread Shawn Weeks
I found the code for it that inserts those like they were attributed in ValueLookup. To further confuse it some processors appear to set an attribute of that name. Thanks for explaining that I was a bit confused. Shawn Weeks Sent from my iPhone On Feb 26, 2019, at 10:54 AM, Mark Payne

Re: TestRunner fileSize Attribute

2019-02-26 Thread Mark Payne
Shawn, I think it is presented that way in the given link because it is accessed via the Expression Language by using ${fileSize} - the same as if it were an attribute. So from the point of view of the user/flow designer, they can be assumed to be the same. However, from the POV of a developer

Re: TestRunner fileSize Attribute

2019-02-26 Thread Matt Burgess
Shawn, Searching the codebase, I couldn't really find (m)any places where "fileSize" is set as a flow file attribute. It is available via the UI (which I presume calls flowFile.getSize()) as well as in provenance events (again populated by flowFile.getSize() not an attribute per se). That

Re: TestRunner fileSize Attribute

2019-02-26 Thread Shawn Weeks
fileSize is listed as a default attribute for a flow file along with uuid and filename. It always seems to be populated in a real workflow. It’s also listed here https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.1.1/bk_getting-started-with-apache-nifi/content/common-attributes.html and

Re: TestRunner fileSize Attribute

2019-02-26 Thread Mark Payne
Hi Shawn, filename and uuid are attributes of the FlowFile. There's no fileSize attribute (unless added explicitly by a processor). You can get the size of a FlowFile by calling FlowFile.getSize() Does that help? Thanks -Mark > On Feb 26, 2019, at 11:20 AM, Shawn Weeks wrote: > > Since