You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Rafael Gomes Fernandes (JIRA)" <ji...@apache.org> on 2016/11/23 16:16:58 UTC

[jira] [Commented] (AIRFLOW-127) Makes filter_by_owner aware of multi-owner DAG

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

Rafael Gomes Fernandes commented on AIRFLOW-127:
------------------------------------------------

I was checking the possibility of a multi-owner DAG and found this JIRA, but Airflow 1.7.1.3 and the dud's changes are not there.
Was dud's changes implemented?

> Makes filter_by_owner aware of multi-owner DAG
> ----------------------------------------------
>
>                 Key: AIRFLOW-127
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-127
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: security, webserver
>            Reporter: dud
>            Assignee: dud
>            Priority: Minor
>
> Hello
> When enabling the _webserver.filter_by_owner_ setting, Airflow issues a request like this one :
> {code}
> SELECT * FROM dag WHERE NOT dag.is_subdag AND dag.is_active AND dag.owners = username
> {code}
> Unfortunately that doesn't account for DAG authored by multiple users.
> Please see my PR : https://github.com/apache/incubator-airflow/pull/1508
> dud



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