Abacn opened a new issue, #25851:
URL: https://github.com/apache/beam/issues/25851

   ### What happened?
   
   Test Link: 
[https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Java_DataflowV2/lastCompletedBuild/testReport/](https://www.google.com/url?q=https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Java_DataflowV2/lastCompletedBuild/testReport/&sa=D&source=buganizer&usg=AOvVaw2J16Rlita3jbVfqCmS1v-Z)
   More Info:
   
   Many FirestoreIO integration test in the Apache Beam Java PostCommit failing 
starting March 14 without code change.
   
   Error Message
   java.util.concurrent.ExecutionException: 
com.google.api.gax.rpc.InvalidArgumentException: 
io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Invalid request routing 
header database=projects/apache-beam-testing/databases/firestoredb. Please fill 
in the request header with format 
x-goog-request-params:project_id=apache-beam-testing&database_id=firestoredb
   
   Firestore recently enforced the routing header for named databases. 
Integration tests need to pass the correct routing header.
   
   ### Issue Failure
   
   Failure: Test is continually failing
   
   ### Issue Priority
   
   Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be 
sure the product is healthy)
   
   ### 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]

Reply via email to