You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Yuvaraj (JIRA)" <ji...@apache.org> on 2018/12/04 10:25:00 UTC
[jira] [Created] (AIRFLOW-3441) Dag View Customization
Yuvaraj created AIRFLOW-3441:
--------------------------------
Summary: Dag View Customization
Key: AIRFLOW-3441
URL: https://issues.apache.org/jira/browse/AIRFLOW-3441
Project: Apache Airflow
Issue Type: Improvement
Components: api, webapp
Reporter: Yuvaraj
Attachments: Screen Shot 2018-12-04 at 3.53.37 PM.png
I have a series of questions as part of airflow UI. Experts please guide.
# Is there a possibility to view DAGS in a folder structure. At present we do have all the DAGS in segregated fashion and we have to filter to get DAGS for a specific project. If dags are represented in terms of subfolder name (Say Project Name) under the MAIN DAG folder. It will be easy to navigate in terms of better operations.
# How to we filter *DAG/TASK* instances using *contains* filter. *Eg:* Dag ID contains <Values> (how multiple values are specified. Is it comma/colon/space separated?)
# Is there a option to *hold/pause* only a individual task instance in a dag. By doing so the next DAG run should also not be coming into queue for execution. Say for activities like fixing a issue/maintenance and then release the task instance to execute.
# How can we monitor the user activities performed on a DAG (Like operating/changing the Dag).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)