You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Niel Markwick (Jira)" <ji...@apache.org> on 2022/03/17 16:58:00 UTC
[jira] [Created] (BEAM-14121) Incorrect Spanner IO Request Count metrics
Niel Markwick created BEAM-14121:
------------------------------------
Summary: Incorrect Spanner IO Request Count metrics
Key: BEAM-14121
URL: https://issues.apache.org/jira/browse/BEAM-14121
Project: Beam
Issue Type: Bug
Components: io-java-gcp
Affects Versions: 2.34.0
Reporter: Niel Markwick
Assignee: Niel Markwick
IO request count metrics calculated incorrectly for GCP Spanner
Resource ID is formulated incorrectly
*Spanner Table:*
{{//spanner.googleapis.com/projects/\{projectId}/{*}topics{*}/\{databaseId}/tables/\{tableId}}}
should be
{{//spanner.googleapis.com/projects/\{projectId}/instances/\{instanceId}/databases/\{databaseId}/tables/\{tableId}}}
and is populated incorrectly – instance ID is used in place of tableID
Spanner SQL Query:
{{//spanner.googleapis.com/projects/\{projectId}/queries/\{queryName} }}
{{should be}}
{{{}//spanner.googleapis.com/projects/\{projectId}/{}}}{{{}instances/\{instanceId}/queries{}}}{{{}/\{queryName} {}}}
and queryName is nullable which cause issued downstream
this is not actually populated at all - queries are logged as reads on an instance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)