You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Qian Yu (Jira)" <ji...@apache.org> on 2020/02/01 10:36:00 UTC
[jira] [Updated] (AIRFLOW-6657) Deprecate BaseBranchOperator
[ https://issues.apache.org/jira/browse/AIRFLOW-6657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qian Yu updated AIRFLOW-6657:
-----------------------------
Summary: Deprecate BaseBranchOperator (was: Implement BranchPythonOperator as BaseBranchOperator)
> Deprecate BaseBranchOperator
> ----------------------------
>
> Key: AIRFLOW-6657
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6657
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 1.10.4
> Reporter: Qian Yu
> Assignee: Qian Yu
> Priority: Major
>
> This PR added a base class {{BaseBranchOperator}} that is intended to let people implement custom branching logic as its subclasses. https://github.com/apache/airflow/pull/5231
> However the existing {{BranchPythonOperator}} is implemented on its own, not utilizing {{BaseBranchOperator}}.
> This is making other JIRAs difficult to continue. E.g. this one AIRFLOW-5391. Should subsequent JIRAs be working on {{BranchPythonOperator}} or {{BaseBranchOperator}} or both?
> There was a discussion about implementing {{BranchPythonOperator}} as {{BaseBranchOperator}}. However, the discussion did not continue to implement it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)