Currently failing reads just throw a SpannerException, without any information about which particular read operation failed. Sometimes due to the way Spanner separates the read API call from the row retrieval, you cannot see from the exception what table/query caused the read to fail.
And an error log to indicate which table /query result was being read when the failure occurred.
What needs to happen?
Currently failing reads just throw a SpannerException, without any information about which particular read operation failed. Sometimes due to the way Spanner separates the read API call from the row retrieval, you cannot see from the exception what table/query caused the read to fail.
And an error log to indicate which table /query result was being read when the failure occurred.
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components