Skip to content
This repository was archived by the owner on Apr 7, 2026. It is now read-only.
This repository was archived by the owner on Apr 7, 2026. It is now read-only.

ListDatabaseOperations should filter on metadata type first, and then metadata field #179

Closed
#180
Closed
ListDatabaseOperations should filter on metadata type first, and then metadata field#179
#180
Assignees
olavloite
Labels
api: spannerIssues related to the googleapis/java-spanner API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
@olavloite

Description

@olavloite
olavloite
opened on Apr 24, 2020

ListDatabaseOperations requests must specify filter options in a specific order:

  • This will fail: (metadata.source_type=BACKUP) (metadata.@type=type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata)
  • This will succeed: (metadata.@type=type.googleapis.com/google.spanner.admin.database.v1.RestoreDatabaseMetadata) (metadata.source_type=BACKUP)

The client library currently creates filters that can contain these fields in the opposite order, which causes RPC's to fail.

Metadata

Metadata

Assignees

Labels

api: spannerIssues related to the googleapis/java-spanner API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions