[jira] [Commented] (AIRFLOW-2964) Lazy generation of the job description

[ https://issues.apache.org/jira/browse/AIRFLOW-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594159#comment-16594159 ] Andrew Chen commented on AIRFLOW-2964: -- My guess is no. Maybe we should post this

[jira] [Commented] (AIRFLOW-2964) Lazy generation of the job description

[ https://issues.apache.org/jira/browse/AIRFLOW-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593997#comment-16593997 ] Andrew Chen commented on AIRFLOW-2964: -- This certainly makes a lot of sense to me,

[jira] [Created] (AIRFLOW-1652) Push DatabricksRunSubmitOperator metadata into XCOM

Andrew Chen created AIRFLOW-1652: Summary: Push DatabricksRunSubmitOperator metadata into XCOM Key: AIRFLOW-1652 URL: https://issues.apache.org/jira/browse/AIRFLOW-1652 Project: Apache Airflow

[jira] [Created] (AIRFLOW-1577) Add token support to DatabricksHook

Andrew Chen created AIRFLOW-1577: Summary: Add token support to DatabricksHook Key: AIRFLOW-1577 URL: https://issues.apache.org/jira/browse/AIRFLOW-1577 Project: Apache Airflow Issue Type: Im

[jira] [Created] (AIRFLOW-1221) Fix DatabricksSubmitRunOperator Templating

Andrew Chen created AIRFLOW-1221: Summary: Fix DatabricksSubmitRunOperator Templating Key: AIRFLOW-1221 URL: https://issues.apache.org/jira/browse/AIRFLOW-1221 Project: Apache Airflow Issue T

[jira] [Created] (AIRFLOW-1140) DatabricksSubmitRunOperator should template the "json" field.

Andrew Chen created AIRFLOW-1140: Summary: DatabricksSubmitRunOperator should template the "json" field. Key: AIRFLOW-1140 URL: https://issues.apache.org/jira/browse/AIRFLOW-1140 Project: Apache Airfl

[jira] [Updated] (AIRFLOW-1101) Docs use the term "Pipelines" instead of DAGs

[ https://issues.apache.org/jira/browse/AIRFLOW-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Chen updated AIRFLOW-1101: - Description: It's a bit confusing to use the words "DAGs" and "pipelines" interchangeably in th

[jira] [Updated] (AIRFLOW-1101) Docs use the term "Pipelines" instead of DAGs

[ https://issues.apache.org/jira/browse/AIRFLOW-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Chen updated AIRFLOW-1101: - Description: It's a bit confusing to use the words "DAGs" and "pipelines" interchangeably in th

[jira] [Created] (AIRFLOW-1101) Docs use the term "Pipelines" instead of DAGs

Andrew Chen created AIRFLOW-1101: Summary: Docs use the term "Pipelines" instead of DAGs Key: AIRFLOW-1101 URL: https://issues.apache.org/jira/browse/AIRFLOW-1101 Project: Apache Airflow Issu

[jira] [Updated] (AIRFLOW-1070) Task instance run should catch SIGINT as well as SIGTERM

[ https://issues.apache.org/jira/browse/AIRFLOW-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Chen updated AIRFLOW-1070: - Priority: Trivial (was: Major) > Task instance run should catch SIGINT as well as SIGTERM > ---

[jira] [Created] (AIRFLOW-1070) Task instance run should catch SIGINT as well as SIGTERM

Andrew Chen created AIRFLOW-1070: Summary: Task instance run should catch SIGINT as well as SIGTERM Key: AIRFLOW-1070 URL: https://issues.apache.org/jira/browse/AIRFLOW-1070 Project: Apache Airflow

[jira] [Work started] (AIRFLOW-1028) Databricks Operator for Airflow

[ https://issues.apache.org/jira/browse/AIRFLOW-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-1028 started by Andrew Chen. > Databricks Operator for Airflow > --- > >

[jira] [Created] (AIRFLOW-1028) Databricks Operator for Airflow

Andrew Chen created AIRFLOW-1028: Summary: Databricks Operator for Airflow Key: AIRFLOW-1028 URL: https://issues.apache.org/jira/browse/AIRFLOW-1028 Project: Apache Airflow Issue Type: New Fe