[GitHub] [beam] TheNeuralBit opened a new issue, #22537: [Feature Request]: Lower log-level for caught error in StorageApiWritesShardedRecords

[GitBox <gi...@apache.org>]

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

   ### What would you like to happen?
   
   We log an error here:
   https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/StorageApiWritesShardedRecords.java#L447-L448
   
   But I've seen that these errors can be benign, e.g. `ALREADY_EXISTS: The offset is within stream, expected offset ...` can happen when re-establishing a stream, but doesn't indicate a failure, so logging it as an error is misleading.
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: io-java-gcp


-- 
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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] TheNeuralBit commented on issue #22537: [Feature Request]: Lower log-level for caught error in StorageApiWritesShardedRecords

[GitBox <gi...@apache.org>]

TheNeuralBit commented on issue #22537:
URL: https://github.com/apache/beam/issues/22537#issuecomment-1199971936

   @reuvenlax should we lower the log level here? I'm not sure if there are other cases where logging an error is appropriate, but it seems like at least in the case I noted it's not.


-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org