falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1755) Workflow owner is falcon user instead of process owner
Date Mon, 18 Jan 2016 13:05:39 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pragya Mittal updated FALCON-1755:
----------------------------------
    Description: 
In case of oozie scheduler , if we schedule a process then the workflow owner is the user
who scheduled the job.
But, in case of native scheduler, if we schedule a process the owner is falcon_owner and not
the process_owner (one who scheduled the process).
This will lead to job failure on hadoop, where the job will expect a queue by name of process_owner
but it will be by falcon_owner which may not exist.

> Workflow owner is falcon user instead of process owner
> ------------------------------------------------------
>
>                 Key: FALCON-1755
>                 URL: https://issues.apache.org/jira/browse/FALCON-1755
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>
> In case of oozie scheduler , if we schedule a process then the workflow owner is the
user who scheduled the job.
> But, in case of native scheduler, if we schedule a process the owner is falcon_owner
and not the process_owner (one who scheduled the process).
> This will lead to job failure on hadoop, where the job will expect a queue by name of
process_owner but it will be by falcon_owner which may not exist.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message