> Apache Beam _can be_ but this person is talking about using it inside of Google (e.g. as the Dataflow API) and with a Google service.
Right, but it sounds like they filed the bug with Apache Beam, not with Google Cloud. Working through the Beam bug tracker means the team behind it doesn't have any context as to what kind of user they are. And even if they said "I'm using this with Google Cloud", the people they're interacting with there aren't necessarily paid to work on Google-related issues. Sure, a better answer (instead of "it's open source; you can fix it") might have been "you should contact your Google Cloud account rep to report this to them", but still, I think OP reported this bug in the wrong place given their expectations of how it should be handled.
Right, but it sounds like they filed the bug with Apache Beam, not with Google Cloud. Working through the Beam bug tracker means the team behind it doesn't have any context as to what kind of user they are. And even if they said "I'm using this with Google Cloud", the people they're interacting with there aren't necessarily paid to work on Google-related issues. Sure, a better answer (instead of "it's open source; you can fix it") might have been "you should contact your Google Cloud account rep to report this to them", but still, I think OP reported this bug in the wrong place given their expectations of how it should be handled.