Re: [D] Is Airflow planning on removing the Operator API to use TaskFlow instead? [airflow]
GitHub user potiuk added a comment to the discussion: Is Airflow planning on removing the Operator API to use TaskFlow instead? Not logic. Use. > they have different intended users Classic operators is for user who prefer more "black-box" and predefined "working operators" put together in a DAG. Task flow is for the users who prefer to write more custom python code. GitHub link: https://github.com/apache/airflow/discussions/45686#discussioncomment-11853276 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] Is Airflow planning on removing the Operator API to use TaskFlow instead? [airflow]
GitHub user NF-ada added a comment to the discussion: Is Airflow planning on removing the Operator API to use TaskFlow instead? Thanks for the clarification! Maybe I missed it but what would you say is the difference or logic for using one or the other? GitHub link: https://github.com/apache/airflow/discussions/45686#discussioncomment-11851788 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] Is Airflow planning on removing the Operator API to use TaskFlow instead? [airflow]
GitHub user potiuk added a comment to the discussion: Is Airflow planning on removing the Operator API to use TaskFlow instead? No.. both interfaces are going to stay. They serve different purposes and have different intended users GitHub link: https://github.com/apache/airflow/discussions/45686#discussioncomment-11846462 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
