You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Yati (JIRA)" <ji...@apache.org> on 2018/01/19 22:09:00 UTC
[jira] [Created] (AIRFLOW-2015) Add an --interactive switch to
`airflow run`
Yati created AIRFLOW-2015:
-----------------------------
Summary: Add an --interactive switch to `airflow run`
Key: AIRFLOW-2015
URL: https://issues.apache.org/jira/browse/AIRFLOW-2015
Project: Apache Airflow
Issue Type: Bug
Components: cli
Reporter: Yati
Assignee: Yati
The command
{code:java}
$ airflow run dag_id task_id xdate
{code}
redirects all output to the configured logger. For development of dags and of airflow itself, it is helpful to be able to put breakpoints in code. Capturing standard output and error streams in this case hinders this use case. Unless there already is a way to work around this, I propose addition of an --interactive. Example:
{noformat}
(airflow) ys@dock:~/incubator-airflow$ airflow run --force --interactive --local leader a '2018-01-16T00:00:00Z'
---logging snipped---
> /home/ys/incubator-airflow/airflow/bin/cli.py(329)_run()
-> if args.local:
(Pdb)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)