[ https://issues.apache.org/jira/browse/AIRFLOW-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234602#comment-16234602 ]
Guillermo RodrÃguez Cano edited comment on AIRFLOW-1774 at 11/1/17 7:19 PM: ---------------------------------------------------------------------------- And the corresponding PR: https://github.com/apache/incubator-airflow/pull/2746 addressing the issue was (Author: wileeam): And the corresponding PR: https://github.com/apache/incubator-airflow/pull/2746 > Better handling of templated parameters in Google ML batch > prediction/training operators > ---------------------------------------------------------------------------------------- > > Key: AIRFLOW-1774 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1774 > Project: Apache Airflow > Issue Type: Improvement > Components: contrib, operators > Affects Versions: Airflow 2.0, 1.9.0 > Reporter: Guillermo RodrÃguez Cano > Priority: Normal > > The {{MLEngineBatchPredictionOperator}} does not support well the templated > parameter {{job_id}} due to a helper function used to detect and cleanup bad > job names inhibiting the templating engine to work. I suspect the same may > happen with {{MLEngineTrainingOperator}} as well. > Google ML requieres a unique job id, therefore it is critical to have the > possibility to customise the job's name easily, and preferably with some data > related to the DAG, for example, appending the day to the job's name via a > macro like {{ds}} -- This message was sent by Atlassian JIRA (v6.4.14#64029)