[
https://issues.apache.org/jira/browse/AIRFLOW-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004900#comment-17004900
]
ASF GitHub Bot commented on AIRFLOW-6356:
-----------------------------------------
potiuk commented on pull request #6951: [AIRFLOW-6356] clear/dag_state should
not show logs from other dags
URL: https://github.com/apache/airflow/pull/6951
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> make cli only print output relevant to dag argument passed in rather than
> from any random dag in bag
> ----------------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-6356
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6356
> Project: Apache Airflow
> Issue Type: Improvement
> Components: cli, DAG
> Affects Versions: 1.10.6
> Reporter: t oo
> Assignee: t oo
> Priority: Major
>
> I have 5 different .py that each generate dynamic dags. One of the .py had a
> bug where it was printing exceptions for dagxyz instead of properly
> generating the dag. the other 4 .py were correctly generating other dags
>
> now when I run airflow cli of 'get_state' dagabc I was not just getting the
> result for dagabc but also seeing the exception log printed related to
> dagxyz! I am sure many other cli commands are affected since the log messages
> from OTHER dags in dagbag are not suppressed
>
> [https://github.com/apache/airflow/blob/1.10.7/airflow/bin/cli.py#L589-L598]
> The cli boasts only getting the state of a DagRun returned, not exception
> logs from other DAGs!
>
> |Returns the state of a DagRun at the command line.|
> | |>>> airflow dag_state tutorial 2015-01-01T00:00:00.000000|
> | |running|
> dag_state and clear commands are definitely impacted (the log shows 'Filling
> up the DagBag from' at folder level)
> trigger_dag command is not impacted (the log shows 'Filling up the DagBag
> from' at .py level)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
