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

Andras Salamon commented on OOZIE-3415:
---------------------------------------

It seems to me [BaseJobsServlet. ensureJobApplicationPath 
|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java#L122]
 also check the value of {{oozie.libpath}}.

> oozie.libpath cannot be used together with oozie.coord.application.path and 
> oozie.bundle.application.path
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3415
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3415
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Andras Salamon
>            Assignee: Andras Salamon
>            Priority: Major
>             Fix For: 5.2.0
>
>
> If {{oozie.libpath}} is specified then 
> [V1JobsServlet.checkAndWriteApplicationXMLToHDFS|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java#L139-L185]
>  will ignore the {{oozie.coord.application.path}} and 
> {{oozie.bundle.application.path}} settings. So it's not possible to specify 
> {{oozie.libpath}} and {{oozie.coord.application.path}} / 
> {{oozie.bundle.application.path}} at the same time in the {{job.properties}} 
> file.
> I don't really see the reason for checking the {{oozie.libpath}} directory 
> when we search for {{workflow.xml}} we should delete this check. If this 
> check is important then we should still check 
> {{oozie.coord.application.path}} and {{oozie.bundle.application.path}} if we 
> found nothing in {{oozie.libpath}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to