Hi Giridhar, There is no setting to override string length in workflow definition file.
I am not sure of your use case. One workaround could be is to parameterized the string in workflow and configure the value in property file. In this way your workflow string length will be within limit and it may succeed. Thanks, Puru. On 11/6/13 8:12 PM, "Giridhar Addepalli" <[email protected]> wrote: >Hi All, > >Is there any way to increase length of strings that can be used in >workflow >definition? > >Thanks, >Giridhar. > > >On Tue, Nov 5, 2013 at 4:58 PM, Giridhar Addepalli ><[email protected]>wrote: > >> Hi All, >> >> I have very long string ( of length 69390 bytes ) in workflow definition >> file. >> OozieClient is throwing exception when i try to submit this workflow. >> >> E0803 : E0803: IO error, java.lang.RuntimeException: >>java.io.UTFDataFormatException: encoded string too long: 69390 bytes >> at >>org.apache.oozie.client.OozieClient.handleError(OozieClient.java:445) >> at >>org.apache.oozie.client.OozieClient$JobSubmit.call(OozieClient.java:523) >> at >>org.apache.oozie.client.OozieClient$JobSubmit.call(OozieClient.java:493) >> at >>org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java: >>416) >> at org.apache.oozie.client.OozieClient.run(OozieClient.java:587) >> at >>com.walmartlabs.dare.oozie.OozieExecutionManager$SubmitCallable.call(Oozi >>eExecutionManager.java:56) >> at >>com.walmartlabs.dare.oozie.OozieExecutionManager$SubmitCallable.call(Oozi >>eExecutionManager.java:45) >> at >>com.walmartlabs.dare.oozie.OozieExecutionManager.resilientOozieCall(Oozie >>ExecutionManager.java:235) >> at >>com.walmartlabs.dare.oozie.OozieExecutionManager.submitToOozie(OozieExecu >>tionManager.java:207) >> at >>com.walmartlabs.dare.oozie.OozieExecutionManager.runExecTask(OozieExecuti >>onManager.java:151) >> at >>com.codeminders.hamake.execution.AbstractExecutionManager.runTask(Abstrac >>tExecutionManager.java:180) >> at >>com.codeminders.hamake.execution.AbstractExecutionManager.access$000(Abst >>ractExecutionManager.java:17) >> at >>com.codeminders.hamake.execution.AbstractExecutionManager$TaskExecutionIn >>fo.run(AbstractExecutionManager.java:47) >> at java.lang.Thread.run(Thread.java:662) >> >> >> Is there a way to by pass this exception? >> >> I came to know of >>"oozie.service.WorkflowAppService.WorkflowDefinitionMaxLength" property >>which can be used to increase workflow definition length. >> >> Is there any similar way to increase length of strings inside workflow >>definition file? >> >> >> Thanks, >> >> Giridhar. >> >>
