falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-332) Oozie execution order is wrongly mapped in Falcon for LAST_ONLY
Date Fri, 07 Mar 2014 00:52:43 GMT

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

Venkatesh Seetharam commented on FALCON-332:
--------------------------------------------

Last only should be quite useful for bulk replication. We use this feature in Ambari. I did
not know this was the case. How hard is it to write a simple tool to convert the old configs
because the ROI on backwards compatibility in this case is high and the code gets brittle.
I'd agree with Shaik that since the process definitions that exist in the config store and
only submitted but never scheduled, a tool to convert this should suffice.

Makes sense?

> 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