You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Peter Attardo (JIRA)" <ji...@apache.org> on 2016/06/16 18:48:06 UTC

[jira] [Updated] (AIRFLOW-250) Add task-specific template searchpaths

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

Peter Attardo updated AIRFLOW-250:
----------------------------------
    Issue Type: Improvement  (was: Bug)

> Add task-specific template searchpaths
> --------------------------------------
>
>                 Key: AIRFLOW-250
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-250
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Peter Attardo
>
> Currently template searchpaths are pulled from the DAG, but there are many instances where we would want a specific task to look in its own folder for its template(s) to avoid name collisions, or to define the template location in the task definition and not have to worry about what DAG it is added to. Adding an optional template_searchpath parameter to BaseOperator that operates similar to, and has precedence over, the DAG's template_searchpath would allow this functionality without impacting existing templating logic.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)