From 44a94339c0c29ea49515b7b8f54cdaeebb49d5d8 Mon Sep 17 00:00:00 2001 From: itsankit-google Date: Mon, 11 Mar 2024 06:15:17 +0000 Subject: [PATCH] Add error message to spanner failure logging --- .../io/cdap/plugin/gcp/spanner/source/SpannerSource.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/main/java/io/cdap/plugin/gcp/spanner/source/SpannerSource.java b/src/main/java/io/cdap/plugin/gcp/spanner/source/SpannerSource.java index ad03c023e..603e38922 100644 --- a/src/main/java/io/cdap/plugin/gcp/spanner/source/SpannerSource.java +++ b/src/main/java/io/cdap/plugin/gcp/spanner/source/SpannerSource.java @@ -131,9 +131,10 @@ public void configurePipeline(PipelineConfigurer pipelineConfigurer) { // this is because spanner exception error message is not very user friendly. It contains class names and new // lines in the error message. collector.addFailure(String.format( - "Unable to connect to spanner instance with error code: %s", e.getErrorCode().name()), + "Unable to connect to spanner instance with error code: %s and error message: %s", + e.getErrorCode().name(), e.getMessage()), "Verify spanner configurations such as instance, database, table, project, etc.") - .withStacktrace(e.getStackTrace()); + .withStacktrace(e.getStackTrace()); } }