Abacn opened a new issue, #25383: URL: https://github.com/apache/beam/issues/25383
### What needs to happen? created from https://github.com/apache/beam/pull/25108#issuecomment-1400709831: When reading from change streams there are two databases involved, 1) the primary database that contains the change stream, and 2) a metadata database (maintained by Beam) that holds partition progress state so a job can be restarted and pick up where it left off. To create a spanner config to access the metadata database, the following pattern is used: ``` SpannerConfig metadataConfig = spannerConfig.toBuilder() .setInstanceId(metadataInstanceId) .setDatabaseId(metadataDatabaseId) .build(); ``` The metadata config (`metadataConfig`) is initialized using the primary database config (`spannerConfig`) since most of the fields are the same and then the ones that are different get overwritten. With the Fine-Grained Access Control project, we've added a new config field _databaseRole_ that should only be set for primary database access. Unfortunately the pattern above blindly copies this field to the metadata config. A better approach would be to write a metadata config create function that copies a whitelisted set of fields from the primary config and leaves all of the other fields empty. ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [X] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [X] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
