Best way to generate oozie workflow programmatically

[Nirmal Kumar <ni...@impetus.co.in>]

Hi Everyone,

I am looking for alternatives where I can programmatically generate Oozie workflows.

One that found is:
Use Java Architecture for XML Binding (JAXB) to generate Java binding (based on the Workflow schema), and use these bindings as a Java API to create Oozie Workflows.

Any other alternatives?

Thanks,
-Nirmal


________________________________






NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.

Re: Best way to generate oozie workflow programmatically

[Jagat Singh <ja...@gmail.com>]

Falcon is using the same approach you suggested for JAXB.

if you want to reuse that code

https://github.com/apache/falcon/tree/master/oozie



On Tue, Jul 28, 2015 at 8:53 PM, Nirmal Kumar <ni...@impetus.co.in>
wrote:

> Hi Everyone,
>
> I am looking for alternatives where I can programmatically generate Oozie
> workflows.
>
> One that found is:
> Use Java Architecture for XML Binding (JAXB) to generate Java binding
> (based on the Workflow schema), and use these bindings as a Java API to
> create Oozie Workflows.
>
> Any other alternatives?
>
> Thanks,
> -Nirmal
>
>
> ________________________________
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>