Yichi Zhang created BEAM-12718:
----------------------------------
Summary: Dataflow runner throws unclear exception when credential
is not set properly
Key: BEAM-12718
URL: https://issues.apache.org/jira/browse/BEAM-12718
Project: Beam
Issue Type: Improvement
Components: runner-dataflow
Reporter: Yichi Zhang
{code:java}
Caused by: java.lang.IllegalArgumentException: Error constructing default value
for gcpTempLocation: tempLocation is not a valid GCS path, gs://....
at
org.apache.beam.sdk.extensions.gcp.options.GcpOptions$GcpTempLocationFactory.create(GcpOptions.java:319)
at
org.apache.beam.sdk.extensions.gcp.options.GcpOptions$GcpTempLocationFactory.create(GcpOptions.java:297)
at
org.apache.beam.sdk.options.ProxyInvocationHandler.returnDefaultHelper(ProxyInvocationHandler.java:605)
at
org.apache.beam.sdk.options.ProxyInvocationHandler.getDefault(ProxyInvocationHandler.java:546)
at
org.apache.beam.sdk.options.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:171)
at com.sun.proxy.$Proxy25.getGcpTempLocation(Unknown Source)
at
org.apache.beam.runners.dataflow.DataflowRunner.fromOptions(DataflowRunner.java:278)
... 16 more
Caused by: java.lang.IllegalArgumentException: Output path does not exist or is
not writeable: gs://...
{code}
When user submits pipeline but the google cloud credential was not set properly
in the terminal, the runner throw above exception, which is confusing.
Proper exception regarding credential issues should be more clear for user to
troubleshoot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
