You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Vardan Gupta (JIRA)" <ji...@apache.org> on 2018/08/06 11:41:00 UTC

[jira] [Assigned] (AIRFLOW-2861) Need index on log table

     [ https://issues.apache.org/jira/browse/AIRFLOW-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vardan Gupta reassigned AIRFLOW-2861:
-------------------------------------

    Assignee: Vardan Gupta

> Need index on log table
> -----------------------
>
>                 Key: AIRFLOW-2861
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2861
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: database
>    Affects Versions: 1.10.0
>            Reporter: Vardan Gupta
>            Assignee: Vardan Gupta
>            Priority: Major
>
> Delete dag functionality is added in v1-10-stable, whose implementation during the metadata cleanup [part|https://github.com/apache/incubator-airflow/blob/dc78b9196723ca6724185231ccd6f5bbe8edcaf3/airflow/api/common/experimental/delete_dag.py#L48], look for classes which has attribute named as dag_id and then formulate the query on matching model and then delete from metadata, we've few numbers where we've observed slowness especially in log table because it doesn't have any single or multiple-column index. Creating an index would boost the performance though insertion will be a bit slower. Since deletion will be a sync call, would be good idea to create index.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)