Thank you, I will try with sub workflow On Aug 17, 2012 10:44 PM, "Alejandro Abdelnur" <[email protected]> wrote:
> Tousif, > > While this will work, keep in mind that the WFs end up in the DB and are > loaded by Oozie when processing the job. This may make the system a bit > slower due to that. > > Also, having a WF over 100K is like having a very large class/method, you'd > be better off if you refactor your workflow in multiple workflows and use > the sub-workflow action from a top level workflow. > > This will also allow you to reuse easily this subworflows from other > workflows. > > Regards > > On Fri, Aug 17, 2012 at 3:36 AM, Tousif <[email protected]> wrote: > > > ok i added this property in oozie site > > > > <property> > > > > <name>oozie.service.WorkflowAppService.WorkflowDefinitionMaxLength</name> > > <value>10000000</value> > > <description> > > The maximum length of the workflow definition in bytes > > An error will be reported if the length exceeds the given > > maximum > > </description> > > </property> > > > > > > On Fri, Aug 17, 2012 at 3:52 PM, Tousif <[email protected]> wrote: > > > > > HI, > > > > > > Where can i set or increase *Workflow definition lenght. I have coord > > > job of map reduce* > > > > > > E0736: Workflow definition lenght [217,869] exceeded maximum allowed > > > length [100,000] > > > > > > -- > > > > > > > > > Regards > > > Tousif Khazi > > > > > > . > > > "A player that makes a team great is more valuable than a great > player". > > > > > > > > > > > > > > > -- > > > > > > Regards > > Tousif Khazi > > > > . > > "A player that makes a team great is more valuable than a great player". > > > > > > -- > Alejandro >
