falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-332) Oozie execution order is wrongly mapped in Falcon for LAST_ONLY
Date Thu, 06 Mar 2014 19:26:43 GMT

    [ https://issues.apache.org/jira/browse/FALCON-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922930#comment-13922930
] 

Shaik Idris Ali commented on FALCON-332:
----------------------------------------

Changing the enum value might cause problems to users who are already using enum. "ONLYLAST".
As the config store might not come up due to validation error as pointed by Shwetha.

Since, such processes are not scheduled, it would be easy to just leave the enum value as
defined in oozie, instead of mapping in feed mapper.

If the possibility of usage this feature is high, we can have code handle this mapping. [~svenkat]
your thoughts.

> Oozie execution order is wrongly mapped in Falcon for LAST_ONLY
> ---------------------------------------------------------------
>
>                 Key: FALCON-332
>                 URL: https://issues.apache.org/jira/browse/FALCON-332
>             Project: Falcon
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.5
>            Reporter: Shaik Idris Ali
>            Assignee: Shaik Idris Ali
>            Priority: Critical
>              Labels: client, process, xsd
>             Fix For: 0.5
>
>         Attachments: FALCON-332.patch
>
>
> Falcon process.xsd has restriction for execution order:
> {code}   
>  <xs:simpleType name="execution-type">
>         <xs:restriction base="xs:string">
>             <xs:enumeration value="FIFO"/>
>             <xs:enumeration value="LIFO"/>
>             <xs:enumeration value="ONLYLAST"/>
>         </xs:restriction>
>     </xs:simpleType>
> {code}
> where as the actual value required is LAST_ONLY
> Otherwise oozie throws exception:
> {code}
> 2014-03-03 13:41:17,912  WARN CoordSubmitXCommand:542 - USER[-] GROUP[-] TOKEN[-] APP[-]
JOB[0012670-140302130514548-oozie-oozi-B] ACTION[-] ERROR:  
> java.lang.IllegalArgumentException: No enum const class org.apache.oozie.client.CoordinatorJob$Execution.ONLYLAST
>         at java.lang.Enum.valueOf(Enum.java:196)
>         at org.apache.oozie.client.CoordinatorJob$Execution.valueOf(CoordinatorJob.java:31)
>         at org.apache.oozie.command.coord.CoordSubmitXCommand.resolveInitial(CoordSubmitXCommand.java:711)
>         at org.apache.oozie.command.coord.CoordSubmitXCommand.basicResolveAndIncludeDS(CoordSubmitXCommand.java:557)
>         at org.apache.oozie.command.coord.CoordSubmitXCommand.submit(CoordSubmitXCommand.java:225)
>         at org.apache.oozie.command.SubmitTransitionXCommand.execute(SubmitTransitionXCommand.java:81)
>         at org.apache.oozie.command.SubmitTransitionXCommand.execute(SubmitTransitionXCommand.java:29)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>         at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message