You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Harish Krishnan <ha...@gmail.com> on 2012/07/13 03:56:31 UTC
Can we substitute variables in
Hi,
I was wondering if it is possible to do
<workflow-app xmlns='uri:oozie:workflow:0.2' name='custom-wf'>
<start to='${myAction}'/>
<action name='action_1'>
......
</action>
<action name='action_2'>
.......
</action>
</workflow-app>
and then define the value in job.properties?
I know that this does not match the reg-ex for the type IDENTIFIER. But is
there by any means I can make this work?
Thanks & Regards,
Harish.T.K
Re: Can we substitute variables in
Posted by Harish Krishnan <ha...@gmail.com>.
https://issues.apache.org/jira/browse/OOZIE-910
I created in JIRA earlier today.
I modified xsd and i'm getting an error message
Error: E0708 : E0708: Invalid transition, node [::start::] transition
[${firstHop}]
Trying to debug this.
Thanks & Regards,
Harish.T.K
On Fri, Jul 13, 2012 at 11:59 AM, Harish Krishnan <
harish.t.krishnan@gmail.com> wrote:
> I modified the xsd. But the changes doesn't seem to be reflected.
> How do i build everything so my xsd changes are propagated?
>
> Thanks & Regards,
> Harish.T.K
>
>
>
> On Fri, Jul 13, 2012 at 10:19 AM, Mona Chitnis <ch...@yahoo-inc.com>wrote:
>
>> Good point Harish!
>>
>> --
>> Mona Chitnis
>>
>>
>>
>>
>> On 7/13/12 10:05 AM, "Harish Krishnan" <ha...@gmail.com>
>> wrote:
>>
>> >Hi,
>> >
>> >I was able to do this. Had to modify the xsd.
>> >
>> > <xs:complexType name="START">
>> > <!--<xs:attribute name="to" type="workflow:IDENTIFIER"
>> >use="required"/>-->
>> > <xs:attribute name="to" type="xs:string" use="required"/>
>> > </xs:complexType>
>> >
>> >This way I can decide which action to run by passing a variable in
>> >job.properties
>> >
>> >Thanks & Regards,
>> >Harish.T.K
>> >
>> >
>> >On Thu, Jul 12, 2012 at 6:56 PM, Harish Krishnan <
>> >harish.t.krishnan@gmail.com> wrote:
>> >
>> >> Hi,
>> >>
>> >> I was wondering if it is possible to do
>> >>
>> >> <workflow-app xmlns='uri:oozie:workflow:0.2' name='custom-wf'>
>> >> <start to='${myAction}'/>
>> >> <action name='action_1'>
>> >> ......
>> >> </action>
>> >> <action name='action_2'>
>> >> .......
>> >> </action>
>> >> </workflow-app>
>> >>
>> >> and then define the value in job.properties?
>> >>
>> >> I know that this does not match the reg-ex for the type IDENTIFIER. But
>> >>is
>> >> there by any means I can make this work?
>> >>
>> >> Thanks & Regards,
>> >> Harish.T.K
>> >>
>>
>>
>
Re: Can we substitute variables in
Posted by Harish Krishnan <ha...@gmail.com>.
I modified the xsd. But the changes doesn't seem to be reflected.
How do i build everything so my xsd changes are propagated?
Thanks & Regards,
Harish.T.K
On Fri, Jul 13, 2012 at 10:19 AM, Mona Chitnis <ch...@yahoo-inc.com>wrote:
> Good point Harish!
>
> --
> Mona Chitnis
>
>
>
>
> On 7/13/12 10:05 AM, "Harish Krishnan" <ha...@gmail.com>
> wrote:
>
> >Hi,
> >
> >I was able to do this. Had to modify the xsd.
> >
> > <xs:complexType name="START">
> > <!--<xs:attribute name="to" type="workflow:IDENTIFIER"
> >use="required"/>-->
> > <xs:attribute name="to" type="xs:string" use="required"/>
> > </xs:complexType>
> >
> >This way I can decide which action to run by passing a variable in
> >job.properties
> >
> >Thanks & Regards,
> >Harish.T.K
> >
> >
> >On Thu, Jul 12, 2012 at 6:56 PM, Harish Krishnan <
> >harish.t.krishnan@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I was wondering if it is possible to do
> >>
> >> <workflow-app xmlns='uri:oozie:workflow:0.2' name='custom-wf'>
> >> <start to='${myAction}'/>
> >> <action name='action_1'>
> >> ......
> >> </action>
> >> <action name='action_2'>
> >> .......
> >> </action>
> >> </workflow-app>
> >>
> >> and then define the value in job.properties?
> >>
> >> I know that this does not match the reg-ex for the type IDENTIFIER. But
> >>is
> >> there by any means I can make this work?
> >>
> >> Thanks & Regards,
> >> Harish.T.K
> >>
>
>
Re: Can we substitute variables in
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
Good point Harish!
--
Mona Chitnis
On 7/13/12 10:05 AM, "Harish Krishnan" <ha...@gmail.com> wrote:
>Hi,
>
>I was able to do this. Had to modify the xsd.
>
> <xs:complexType name="START">
> <!--<xs:attribute name="to" type="workflow:IDENTIFIER"
>use="required"/>-->
> <xs:attribute name="to" type="xs:string" use="required"/>
> </xs:complexType>
>
>This way I can decide which action to run by passing a variable in
>job.properties
>
>Thanks & Regards,
>Harish.T.K
>
>
>On Thu, Jul 12, 2012 at 6:56 PM, Harish Krishnan <
>harish.t.krishnan@gmail.com> wrote:
>
>> Hi,
>>
>> I was wondering if it is possible to do
>>
>> <workflow-app xmlns='uri:oozie:workflow:0.2' name='custom-wf'>
>> <start to='${myAction}'/>
>> <action name='action_1'>
>> ......
>> </action>
>> <action name='action_2'>
>> .......
>> </action>
>> </workflow-app>
>>
>> and then define the value in job.properties?
>>
>> I know that this does not match the reg-ex for the type IDENTIFIER. But
>>is
>> there by any means I can make this work?
>>
>> Thanks & Regards,
>> Harish.T.K
>>
Re: Can we substitute variables in
Posted by Harish Krishnan <ha...@gmail.com>.
Hi,
I was able to do this. Had to modify the xsd.
<xs:complexType name="START">
<!--<xs:attribute name="to" type="workflow:IDENTIFIER"
use="required"/>-->
<xs:attribute name="to" type="xs:string" use="required"/>
</xs:complexType>
This way I can decide which action to run by passing a variable in
job.properties
Thanks & Regards,
Harish.T.K
On Thu, Jul 12, 2012 at 6:56 PM, Harish Krishnan <
harish.t.krishnan@gmail.com> wrote:
> Hi,
>
> I was wondering if it is possible to do
>
> <workflow-app xmlns='uri:oozie:workflow:0.2' name='custom-wf'>
> <start to='${myAction}'/>
> <action name='action_1'>
> ......
> </action>
> <action name='action_2'>
> .......
> </action>
> </workflow-app>
>
> and then define the value in job.properties?
>
> I know that this does not match the reg-ex for the type IDENTIFIER. But is
> there by any means I can make this work?
>
> Thanks & Regards,
> Harish.T.K
>