Or use java actions to have better integration/API points between external system and Oozie workflows, such as getting counters, process export properties, etc.
On Fri, Sep 4, 2015 at 4:17 AM, Oren Mazor <[email protected]> wrote: > We've gotten this working by generally just sticking to shell actions, > which can do all of the above > On Thu, Sep 3, 2015 at 9:59 PM ron visbord <[email protected]> wrote: > > > Hello, > > > > My name is Ron. My organization uses Oozie as it's main workflow and > > coordination engine. Over 200 flows are coordinated in our production > > environment. > > > > Many of the developers have recurring demands to be run in oozie. A few > > examples would be > > > > - running data validation using Junit > > - administering Elastic search as part of an ETL flow > > > > These tasks are not always hadoop oriented but the are part of data flows > > which are built and executed in hadoop. > > > > We would very much like to aid these developers and supply them with a > > built-in ability to execute such actions, however I am having a hard time > > finding a definitive, *elaborate* *guide to writing custom actions*. > > > > Other than that, there is absolutely no online material about extending > Hue > > to contain new custom actions. > > > > > > Are there guide for these tasks? > > Can you please refer me? > > > > Thank you very much, > > Ron. > > > > p.s. - our production environment is CDH 5.4 > > >
