H13-723_V2.0 · Question #8
In FusionInsight HD, which method of the OozieClient class will be called by the JAVA API of the Oozie client when running tasks?
The correct answer is D. run. run() is correct because the Oozie Java API's OozieClient.run() method both submits and immediately starts execution of a workflow job in a single call - which is the standard way to "run a task" programmatically in FusionInsight HD. A (suspend) - suspend() pauses a job that is…
Question
In FusionInsight HD, which method of the OozieClient class will be called by the JAVA API of the Oozie client when running tasks?
Options
- Asuspend
- BgetJobInfo
- Csubmit
- Drun
How the community answered
(26 responses)- A4% (1)
- B15% (4)
- C8% (2)
- D73% (19)
Explanation
run() is correct because the Oozie Java API's OozieClient.run() method both submits and immediately starts execution of a workflow job in a single call - which is the standard way to "run a task" programmatically in FusionInsight HD.
- A (suspend) -
suspend()pauses a job that is already running; it has nothing to do with initiating execution. - B (getJobInfo) -
getJobInfo()is a read-only query that retrieves status/metadata about an existing job; it performs no execution. - C (submit) -
submit()only registers the job with the Oozie server and returns a job ID without starting it; a separatestart()call would then be needed to begin execution.
Memory tip: Think of run() as the "one-shot" method - it collapses submit + start into a single step, which is exactly what you'd want when the goal is simply to run a task right away.
Topics
Community Discussion
No community discussion yet for this question.