[
https://issues.apache.org/jira/browse/AIRFLOW-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Payne updated AIRFLOW-2753:
-----------------------------------
Description: I'd like to be able to get the {{jobId}} that's submitted by
the {{DataProcHook}} in order to do things like build the URL to the Dataproc
job UI, etc. The {{job_name}} that the caller passes into
{{DataProcPySparkOperator}}, etc gets an 8 character random string appended to
it before the job is submitted. I don't currently see a way to access that
value, which is needed for the above mentioned use case. (was: I'd like to be
able to get the {{job_name}} that's submitted by the {{DataProcHook}} in order
to do things like build the URL to the Dataproc job UI, etc. The {{job_name}}
that the caller passes into {{DataProcPySparkOperator}}, etc gets an 8
character random string appended to it before the job is submitted. I don't
currently see a way to access that value, which is needed for the above
mentioned use case.)
> dataproc_operator job operators provide a way to get the actual jobId
> submitted to Dataproc
> -------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-2753
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2753
> Project: Apache Airflow
> Issue Type: Improvement
> Components: contrib, operators
> Reporter: Jeffrey Payne
> Assignee: Jeffrey Payne
> Priority: Minor
> Labels: dataproc, google, google-compute-engine, operator
>
> I'd like to be able to get the {{jobId}} that's submitted by the
> {{DataProcHook}} in order to do things like build the URL to the Dataproc job
> UI, etc. The {{job_name}} that the caller passes into
> {{DataProcPySparkOperator}}, etc gets an 8 character random string appended
> to it before the job is submitted. I don't currently see a way to access
> that value, which is needed for the above mentioned use case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
