[ https://issues.apache.org/jira/browse/BEAM-14121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550065#comment-17550065 ]
Danny McCormick commented on BEAM-14121: ---------------------------------------- This issue has been migrated to https://github.com/apache/beam/issues/21635 > 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 > Priority: P2 > Labels: google-cloud-spanner > Original Estimate: 40h > Time Spent: 3h 50m > Remaining Estimate: 36h 10m > > 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.7#820007)