You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kamil Bregula (Jira)" <ji...@apache.org> on 2020/02/02 07:22:00 UTC
[jira] [Commented] (AIRFLOW-6242) Introduce run_type in DAG Run
table
[ https://issues.apache.org/jira/browse/AIRFLOW-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028300#comment-17028300 ]
Kamil Bregula commented on AIRFLOW-6242:
----------------------------------------
We have one more prefix - "manual":
[https://github.com/apache/airflow/blob/41a9bfd/airflow/api/common/experimental/trigger_dag.py#L72]
> Introduce run_type in DAG Run table
> -----------------------------------
>
> Key: AIRFLOW-6242
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6242
> Project: Apache Airflow
> Issue Type: Bug
> Components: backfill, scheduler
> Affects Versions: 1.10.6
> Reporter: Kamil Bregula
> Priority: Major
>
> Hello,
> Before you start reading this ticket, I want to tell you one thing - you are wonderful.
> We use queries that use like expressions to filter two types of DAG Run.
> * Backfill:
> [https://github.com/apache/airflow/blob/699aea8ee368abcba29d717daf2580f897ab9d93/airflow/jobs/backfill_job.py#L52]
> * Scheduled
> [https://github.com/apache/airflow/blob/699aea8ee368abcba29d717daf2580f897ab9d93/airflow/models/dagrun.py#L46]
> This type of expression can affect performance and it seems a better idea to store this information in a separate column. This may allow a query planner to create a better query plan in the database engine.
> Thanks for reading this ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)