Etienne.
Is this what you're looking for?
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#hostname
Thanks,
Phil
On Wed, Feb 14, 2024 at 5:41 AM Etienne Jouvin
wrote:
> Hello.
>
> Imagine, I use UpdateAttributes to set an attribute where I put the NiFi
> instance id
This is proving to be difficult to do in practice. Many of the filenames in
the zip contain spaces and other characters, and these are failing to be
passed to the tar successfully.
This is the command I am testing at the command line to first extract the
filenames:
unzip -l
Please send an email to users-unsubscr...@nifi.apache.org !
More info: https://nifi.apache.org/community/contact/
On Thu, Feb 15, 2024 at 4:54 PM Martin, Stanley L <
stanley.mar...@hexagonusfederal.com> wrote:
>
>
>
>
>
>
Richard,
It sounds like your scripted reader is responsible for parsing the Avro? In
short, the Record appears to have an Avro Utf8 value, not a String, in the
field you’re looking at. You could call .toString() on that Utf8 object, or you
could configure the Avro reader to return Strings
This email message has been delivered safely and archived online by Mimecast.
For more information please visit http://www.mimecast.com
This [1] blog seems amazingly appropriate and wow do we need these/any such
fields we intend to truly honor in a prominent place in the docs. Super
useful...
[1] https://jameswing.net/nifi/nifi-internal-fields.html
Thanks
On Thu, Feb 15, 2024 at 8:35 AM Mark Payne wrote:
> Jim,
>
> You can
Jim,
You can actually reference “lastQueueDate” in Expression Language. It is
formatted as number of milliseconds since epoch.
So you might have a RouteOnAttribute that has a property named “old” with a
value of:
${lastQueueDate:lt( ${now():minus(1)} )}
So any FlowFile that has been
That would work - what a good suggestion. I'll do that. I can format the
resulting number and then RouteOnAttribute by the desired subset of the
result.
Something like this to set attribute dt.failure:
${now():toNumber():toDate("-MM-ddHH:mm:ss"):format("MMddHHmmss","EST")}
Then I can
You could add an UpdateAttribute processor first in the failure path to add a
new attribute which contains the time the error occurred by using the ${now()}
or ${now():toNumber()} expression language function.
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now
Then
As it turns out lineageStartDate and Queued Duration are very different.
Without being able to get at Queued Duration as an attribute, it appears we
cannot RouteOnAttribute to filter thousands in a queue by anything like
hours they have been in queue.
Why would this be helpful? Let us say we have
Hi,
This is a test pipeline reading pdf files from disk. It begins with a
GetFile processor supplying a ConvertRecord processor with a scripted
reader input and an avrorecordsetwriter, generic output.
The scripted reader places the file content in a "content" field:
List recordFields = []
11 matches
Mail list logo
