[jira] [Commented] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set

[ https://issues.apache.org/jira/browse/OOZIE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811476#comment-16811476 ] Andras Salamon commented on OOZIE-3458: --- The patch was accidentally uploaded to an incorrect jira,

[jira] [Commented] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set

[ https://issues.apache.org/jira/browse/OOZIE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805289#comment-16805289 ] Jerry Chabot commented on OOZIE-3458: - I've decided to use cron jobs to submit workflow jobs since we

[jira] [Commented] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set

[ https://issues.apache.org/jira/browse/OOZIE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804883#comment-16804883 ] Jerry Chabot commented on OOZIE-3458: - Unfortunately, this means we need a workaround because EMR

[jira] [Commented] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set

[ https://issues.apache.org/jira/browse/OOZIE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804692#comment-16804692 ] Andras Salamon commented on OOZIE-3458: --- Could you please check OOZIE-3415? It looks very similar