Member since
07-29-2020
574
Posts
318
Kudos Received
175
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
37 | 12-20-2024 05:49 AM | |
44 | 12-19-2024 08:33 PM | |
83 | 12-19-2024 06:48 AM | |
97 | 12-17-2024 12:56 PM | |
100 | 12-16-2024 04:38 AM |
06-04-2022
07:54 AM
Try this: end_next_year = datetime.strptime(current_date,'%Y-%m-%d').replace(year = datetime.strptime(current_date,'%Y-%m-%d').year+1).strftime('%Y%m%d')
... View more
06-03-2022
05:11 PM
1 Kudo
set the date filter as follows: date_filter = datetime.strptime(current_date,'%Y-%m-%d').replace(day =11).strftime('%Y%m%d') If that solves your problem please accept solution. Thanks
... View more
06-03-2022
03:54 PM
1 Kudo
Hi, I think something is happening when nifi is trying to interpret the correct data type in python. to make it work make the current_date string as follows: current_date= str(datetime.today().date()) and let the python engine do the conversion to the correct datetime type when you set the date_filter as follows: date_filter = str(datetime.strptime(current_date,'%Y-%m-%d').replace(day =11)) Not sure if this is a bug in Nifi, but at least this should be a work around. Hope that helps.
... View more
06-03-2022
08:28 AM
Hi, Not sure if this is a bug or what. I have tried the same flow with version 1.16 and got the same behavior. As an alternative I would suggest to use ControlRate Processor where you can set the properties as follows: Rate Control Criteria: flowfile count Maximum Rate : Set to the maximum value that you can have in the queue before nifi applies back pressure. Default value for one node is 10K. Time Duration: 24 hours. Hope that helps.
... View more
05-31-2022
05:55 PM
Hi, What are you trying to do with those attributes? It doesnt make sense that you need to create an attribute for each year value
... View more
05-25-2022
08:18 AM
In this case I would suggest you write custom code through ExecuteScript processor to see if you can retrieve such error message. Not sure what else you can do. sorry
... View more
05-25-2022
08:03 AM
I'm not sure why your spec is producing this result, but to resolve it you can do the transformation on two shift operations: First to flatting json and move the subarray level to the root level and second to move the result and store it into an Array. Here is the spec I tried and it worked: [ { "operation": "shift", "spec": { "MainArray": { "*": "ResultArray.&", "Subarray": { "*": "ResultArray.&" } } } }, { "operation": "shift", "spec": { "ResultArray": { "*": { "$": "ResultArray[#2][0]", "@": "ResultArray[#2][1]" } } } } ]
... View more
05-25-2022
07:06 AM
The ValidateXML processor will write the error to the attribute "validatexml.invalid.error". Check for that attribute when the flowfile is directed to the invalid relationship. Hope that helps
... View more
05-24-2022
05:43 AM
2 Kudos
Hi, Since you are looking for the DB auto generated ID for the City , your best option is to use the LookupRecord Processor , so the flow if your datapipeline will look something like this: GetFile Processor (To the content of the CSV) SplitRecord ( to split Records in the CSV) [Insert the City Info to the DB First] LookupRecord ( to get the ID of the City and enrich you CSV with ID. The Lookup Service should be DB Lookup Service that points to the City Table and Use City Name as Key) [Finally Insert the Person Information with City ID added to the original csv record] To Learn more about LookupRecord, you can watch this video: https://www.youtube.com/watch?v=bSJ5reO8AA4 To learn more about the L
... View more
05-21-2022
08:27 AM
3 Kudos
Hi, After some research I found in order to avoid getting the 403 error, you need to provide the User-Agent to the header as explained by the FAQ under the same domain (scroll below until you find 403 error): https://weather-gov.github.io/api/general-faqs To solve your problem you need to set the UserAgent Property on the invokeHttp processor. It can be something like: nifi/version 1.16.0 Hope that helps, if it does please accept solution. Thanks
... View more