Re: Oozie Job + Version Control Tool

I'd like to pour this conversation into https://issues.apache.org/jira/browse/OOZIE-2876 and it's subtasks. It looks like those action types are trying to solve these issues. Please share your thoughts on this approach there. Thanks! gp On Mon, Oct 31, 2016 at 8:12 AM, goun na

Re: Oozie Job + Version Control Tool

Here's a pom, but I don't think it will tell you much. http://maven.apache.org/POM/4.0.0; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;> hbase-to-hdfs-parent

Re: Oozie Job + Version Control Tool

Per Ullberg, a snippet of pom.xml would help us. :) Thanks, 2016-10-20 3:36 GMT+09:00 Per Ullberg : > @goun na: we keep one coordinator per (zip|war|jar) > > @shiva: I'm happy to share, but it's hard to know what you're in need of. > Ask and I will try to answer :) > >

Re: Oozie Job + Version Control Tool

Thank you for good answers! Adding coordinator version name is also a good idea that I've never thought of. Per Ullberg, do you make a package per a coordinator or workflow? I am not sure putting all coordinator/workflow in a jar/war file. 2016-10-19 17:49 GMT+09:00 Per Ullberg

Re: Oozie Job + Version Control Tool

Hi, Oozie does not have version control for jobs. When you submit a workflow/coordinator/bundle to oozie, it stores it into DB uses it from there for further execution. Thanks, Abhishek > On Oct 19, 2016, at 1:16 PM, goun na wrote: > > Hi users, > > What is the best to

Oozie Job + Version Control Tool

Hi users, What is the best to manage Oozie jobs? Is there a built-in version control feature? Best, Goun Na