About breandan_parlan

breandan_parlan · ‎09-29-2016

I'm looking to create a file named _SUCCESS in a HDFS location containing some attributes. I reckon I could do this using a script processor but is there another way?

breandan_parlan · ‎09-29-2016

Hi, I have a simple workflow whereby a flowfile is passed into an ExecuteScript processor. This runs the following python in the Script Body: ff = session.create() session.transfer(ff, REL_SUCCESS) This transfers the flowfile to the success path, however, the flowfile is never removed from the input queue and thus continues to execute again and again. How do I remove it from the input queue once the script has run? p.s. Is there any documentation for this? Best I have found is the (unofficial?) http://funnifi.blogspot.co.uk/2016/02/executescript-processor-hello-world.html Cheers, Breandán

breandan_parlan · ‎08-02-2016

Did anyone manage to get any further with this?

breandan_parlan · ‎03-03-2016

https://community.hortonworks.com/questions/20963/jobtracker-jobproperties-setting-not-being-respect.html 🙂

breandan_parlan · ‎03-02-2016

I'm having the same issue. The jobTracker port in my workflow/job.properties is set to 8050 (to match the yarn setting) and I can see in the oozie UI (click on job > action > action configuration) that 8050 is being used: ... <job-tracker>mydomain:8050</job-tracker> ... But when I drill down into the hadoop job history logs I see the error: Call From mydomain to 0.0.0.0:8032 failed on connection exception: java.net.ConnectException: Connection refused Where is it pulling 8032 from? Why does it not use the port configured in the job.properties? "The workflow only started to work once I changed both of these to 8032" I'd rather not do this, is there a way to get it to respect the port in the job.properties?

Online	Offline
Last Visited	‎06-05-2018 03:19 PM

Member Since	‎03-02-2016 05:19 PM
Last Visited	‎06-05-2018 03:19 PM
Posts	16
Kudos received	12

Cloudera Community

Create File Using NiFi

Removing flowfile from queue in ExecuteScript Proc...

Re: Spark action always submit to 0.0.0.0:8032

Re: Oozie SparkAction failing

Re: Oozie SparkAction failing