airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Chow (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRFLOW-2469) example task in documentation causes dataflow operator to fail
Date Wed, 16 May 2018 02:24:00 GMT
Chris Chow created AIRFLOW-2469:
-----------------------------------

             Summary: example task in documentation causes dataflow operator to fail
                 Key: AIRFLOW-2469
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2469
             Project: Apache Airflow
          Issue Type: Bug
          Components: Dataflow
    Affects Versions: 1.9.0
            Reporter: Chris Chow


https://github.com/apache/incubator-airflow/blob/c7a472ed6b0d8a4720f57ba1140c8cf665757167/airflow/contrib/operators/dataflow_operator.py#L176
{noformat}
t1 = DataflowTemplateOperator(
task_id='datapflow_example',
template='{{var.value.gcp_dataflow_base}}',
parameters={
'inputFile': "gs://bucket/input/my_input.txt",
'outputFile': "gs://bucket/output/my_output.txt"
},
gcp_conn_id='gcp-airflow-service-account',
dag=my-dag){noformat}
If you actually name a dataflow task 'datapflow_example', the Google dataflow service will
not accept the job because it is not named correctly. Dataflow job names can't have '_' in
them. Strictly speaking, apache beam jobnames must adhere to the regex 

[a-z]([-a-z0-9]*[a-z0-9])?.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message