airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Van Boxel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-589) Google DataProc add job_name as temperable parameter
Date Sun, 23 Oct 2016 09:41:58 GMT

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

Alex Van Boxel updated AIRFLOW-589:
-----------------------------------
    Description: 
The jobname is the name that will appear in the DataProc web console.
It's helpfull to have a one-to-one mapping between the airflow task and
the job running on the cluster. Adding a templated parameter will allow
you to customize how airflow will construct the jobname.

The default is to add the {{task_id}} + {{ds_nodash}} + random hash.

> Google DataProc add job_name as temperable parameter
> ----------------------------------------------------
>
>                 Key: AIRFLOW-589
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-589
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: gcp
>            Reporter: Alex Van Boxel
>            Assignee: Alex Van Boxel
>              Labels: gpc
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The jobname is the name that will appear in the DataProc web console.
> It's helpfull to have a one-to-one mapping between the airflow task and
> the job running on the cluster. Adding a templated parameter will allow
> you to customize how airflow will construct the jobname.
> The default is to add the {{task_id}} + {{ds_nodash}} + random hash.



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

Mime
View raw message