airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ash Berlin-Taylor <...@apache.org>
Subject Re: [2.0 spring cleaning] Remove `dag >> task`?
Date Wed, 03 Jul 2019 12:49:52 GMT
I'm just suggesting removing the `dag >> task` -- `task >> task` will stay

> On 3 Jul 2019, at 13:46, Philippe Gagnon <philgagnon1@gmail.com> wrote:
> 
> Just to be clear, are you suggesting removing all bitshift operator
> overloads from airflow operators (sorry - the dual meaning of operator here
> is confusing), or just the assignment to DAG behavior?
> 
> If it's the former, I find it to be a particularly expressive way to define
> dependencies between tasks so I would vote to keep it as is. The latter
> usage is much less useful, so I would be +1 on removing it.
> 
> On Wed, Jul 3, 2019 at 8:42 AM Ash Berlin-Taylor <ash@apache.org> wrote:
> 
>> It is possible to assign a task to the dag using the bitshift operators,
>> however it doesn't pick up default_args when done this way <
>> https://issues.apache.org/jira/browse/AIRFLOW-883>:
>> 
>> ```
>> dag = DAG('my_dag', default_args=default_args)
>> dummy = DummyOperator(task_id='dummy')
>> 
>> dag >> dummy
>> ```
>> 
>> We could fix that, but how about instead we remove this way of assigning
>> tasks to dags, leaving the context manager (`with dag:`) and other
>> constructions (`Operator(..., dag=dag)`)
>> 
>> Thoughts?
>> 
>> 


Mime
View raw message