About SAMSAL

SAMSAL · ‎10-07-2021

I think I know what is the problem. Since you are not doing any fragmentation -like in using split processor- try setting the Support Fragmented Transaction to False in the PUTSQL. Also remove the original \ failure connection from the Convert processor. you can mute those relationship in the convert setting table by checking the box.

SAMSAL · ‎10-06-2021

Hi, You seem to be having the correct processors and sequence. Can you share screenshot with the configuration of the put SQL. Have you configured the PUTSQL with the correct DB connection? Also are you seeing data (FlowFiles) flowing into it from the above processors. It could be that you are not getting any data to begin with or your configuration in the putSQL is incorrect. By the way why are you connecting failuer,original, sql relationship from the ConvertJsonTOSQL to the PUT SQL? you will get an error this way, you need to just connect the sql releationship. Another thing , the SQL property in the PUTSQL needs to be empty so that it process the sql received from the convert processor, if you have anything in there it will not take the sql insert from the convert processor

SAMSAL · ‎10-06-2021

Take a look at the Nifi ListFile & Fetch File processors. They both work together. The ListFile will read files metadata based on the last read file modified date and will keep state of that so that only newly added files will be read. The fetch file will take the filename parameter from the ListFile processor and fetch the contents. Hope that helps

SAMSAL · ‎10-04-2021

Can some one help verify this please. Im thinking that there is bug in the 1.14 version around this, because I have tried the same ReportingTask on version 1.11.4 against the same Azure Log Analytics workspace ID and Key and its working, so that tells me its not something with Azure. Both versions have the same settings when it comes to nifi.web.https and nifi.remote.input properties except for nifi.remote.input.socket.port where its set for different ports. Thank you.

SAMSAL · ‎10-01-2021

Hi, Im having strange situation and I would really appreciate your help. Basically I was able to setup AzureLogAnalyticsReportingTask (Nifi 1.14) on a cluster and it was working after providing the Workspace ID and Key so I was able to see the log under Azure CustomLog and create my queries and dashboard, however after couple of days it started generating the following error: AzureLogAnalyticsReportingTask [id=] Failed to publish metrics to Azure Log Analytics: java.lang.RuntimeException: HTTP/1.1 403 Forbidden Not sure what happened. I re enter the workspace ID and Key but that did not help. Cam you please help. Thanks

SAMSAL · ‎09-27-2021

I think the problem is that you are trying to evaluate path on a list of sensors: sensor":[{"sensor_id":"Data05_37_alarm","value ":"0"},{"sensor_id":"Data06_37_alarm","value":"0"}.... you probably need to flatten json first and if you are trying to get each sensor information then you need to do splitjson and then you can do evaluatejsonpath. Hope that helps.

SAMSAL · ‎09-25-2021

Its Solved after upgrading to 1.14.0

SAMSAL · ‎09-25-2021

Its Solved in the latest version 1.14.0. I'm not sure if they addressed this issue in later releases of 1.13 version

SAMSAL · ‎07-16-2021

This appears to be fixed in the latest release 1.14.0. I will mark this as resolved. thanks

SAMSAL · ‎06-20-2021

Hi, I have downloaded the latest version of Nifi 1.13.2. In one of my flows Im using an Execute script processor that utilizes python engine which I know it was working without problems in an older (version 1.11.4). I noticed when the processor executes for the first time it works then if you stop it and re run again it hangs and the flow files get stuck in the upstream queue. Initially I thought something in my script is causing the issue so I change it to something as simple as this flowFile = session.get() if flowFile != None: # All processing code starts at this indent session.transfer(flowFile, REL_SUCCESS) Even with this simple script the processor hangs and the flow files remain in the queue. This is a major issue and its causing me not to upgrade. Not sure if you are aware of it and if if there is anything that can be done to mitigate. please advise.

Online	Offline
Last Visited	‎11-03-2024 04:30 AM

Member Since	‎07-29-2020 02:31 PM
Last Visited	‎11-03-2024 04:30 AM
Posts	540
Kudos received	289

Cloudera Community

Re: Unable to successfully use SQL processors afte...

Re: NiFi 2.0.0 - Custom Python Processor Uploading...

Re: ExecuteSQL dynamic query does not work but no ...

Re: Apache Nifi DuplicateFlowFile processor usage ...

Re: Extract char from a String in a flow file

Re: How to use putSQL in nifi

Re: How to use putSQL in nifi

Re: How to schedule process to fetch only new file...

Re: AzureLogAnalyticsReportingTask Failed to Publ...

AzureLogAnalyticsReportingTask Failed to Publish ...

Re: How do we solve this?

Re: Major issue with the ExecuteScript using Pytho...

Re: Major issue with the ExecuteScript using Pytho...

Re: Major issue with the ExecuteScript using Pytho...

Major issue with the ExecuteScript using Python in...