Member since
10-19-2014
58
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5868 | 03-20-2016 10:41 PM | |
10790 | 04-26-2015 02:30 AM |
04-29-2015
08:56 PM
Got it thanks!
... View more
04-29-2015
08:32 PM
Ah, my bad, thanks. That shows oozie_jobs_count = 100, so obviously the change is not picked up. Is /etc/hue/conf/hue.ini the right file (CM is being used)?
... View more
04-29-2015
07:03 PM
Hi Romain, thanks for your response. Unfortunatelly that didn't work, I uncommented that line (under /etc/hue/conf/hue.ini) and changed to 500. This had no effect. Also wanted to check using the dump_config, but http://hue:port/dump_config is giving page me not found. This is on CDH 5.3.1. Thanks, Martin
... View more
04-29-2015
01:05 PM
Thanks for the response. I guess it's not the most intuitive thing in the world and not sure how much value it adds (as you point out, the status is available in profile details). Thanks, Martin
... View more
04-29-2015
01:03 PM
Hello, By default the Oozie workflow dashboard in Hue (Workflows > Dashboard > Workflows) shows 100 completed entries. Is there a way to see more than 100 entries on this screen, or to get to the details (e.g. in order to re-run a failed workflow) for entries beyond the 100 cut off point? Thanks, Martin
... View more
Labels:
- Labels:
-
Apache Oozie
-
Cloudera Hue
04-28-2015
12:08 AM
Hello, Just a question - when I see a list of posts, some author names are appearing in blue and some in black. What is the logic and difference between these? Thanks, Martin
... View more
04-27-2015
11:36 PM
Hello, Using Hue and Oozie, how can I run a specific workflow or action within a workflow as another user? I have tried the following: Workflow Properties > Oozie parameters > user.name - this has no effect Workflow Properties > Hadoop job properties > user.name - this fails with an error Action > Job properties > user.name - this fails with an error The error message for 2 and 3 is as follows: ErrorType [FAILED], ErrorCode [JA010], Message [JA010: Property [user.name] not allowed in action [inline configuration] configuration]
org.apache.oozie.action.ActionExecutorException: JA010: Property [user.name] not allowed in action [inline configuration] configuration
at org.apache.oozie.action.hadoop.JavaActionExecutor.checkForDisallowedProps(JavaActionExecutor.java:198)
at org.apache.oozie.action.hadoop.JavaActionExecutor.parseJobXmlAndConfiguration(JavaActionExecutor.java:451)
at org.apache.oozie.action.hadoop.JavaActionExecutor.setupActionConf(JavaActionExecutor.java:468)
at org.apache.oozie.action.hadoop.ShellActionExecutor.setupActionConf(ShellActionExecutor.java:55)
at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:893)
at org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1145)
at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:228)
at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:63)
at org.apache.oozie.command.XCommand.call(XCommand.java:281)
at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:323)
at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:252)
at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:174)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) Any suggestions? Thanks, Martin
... View more
Labels:
- Labels:
-
Apache Oozie
04-26-2015
02:30 AM
1 Kudo
Hi Harsh, thanks for the follow up, though it's not 100% clear from the response what needs to be done. However, I was able to figure out the following & posting here for the benefit of the community. In the subworkflow task, you can use the Job Properties box to achieve this, e.g. Property Name = PARAM1 Property Value = ${wf:actionData('ParentWFAction')['PARAM_NAME']} Then in the subworkflow itself, you will be able to access the value as ${PARAM1}. Regards, Martin
... View more
04-25-2015
08:52 PM
For the benefit of community members: Cloudera support team confirmed that an updated workflow definition is NOT picked up by an existing submitted coordinator schedule. The workarounds are either to kill the coordinator schedule and resubmit, or to submit the workflow manually which will force the workflow.xml to be updated. Martin
... View more
04-22-2015
12:39 AM
Hello, Is it possible to pass parameters to oozie subworkflows from the parent workflow actions using the actionData funciton, i.e. ${wf:actionData('ParentWFAction')['PARAM_NAME']}? Thanks, Martin
... View more
Labels:
- Labels:
-
Apache Oozie