Per, Your approach seems very interesting. Could you elaborate more on your approach?
Thanks, Shiva On Wed, Oct 19, 2016 at 2:19 PM, Per Ullberg <per.ullb...@klarna.com> wrote: > We package our oozie jobs with maven and release artifacts to nexus. We > keep the version number as part of the coordinator name. That way we have > full traceability between code base and running coordinators. > > regards > /Pelle > > On Wed, Oct 19, 2016 at 10:05 AM, Abhishek Bafna <bafna.i...@gmail.com> > wrote: > > > 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 <gou...@gmail.com> wrote: > > > > > > Hi users, > > > > > > What is the best to manage Oozie jobs? Is there a built-in version > > control > > > feature? > > > > > > Best, > > > Goun Na > > > > > > > -- > > *Per Ullberg* > Data Vault Tech Lead > Odin Uppsala > +46 701612693 <+46+701612693> > > Klarna AB (publ) > Sveavägen 46, 111 34 Stockholm > Tel: +46 8 120 120 00 <+46812012000> > Reg no: 556737-0431 > klarna.com >
