-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: we should isolate the client used in StreamWriter and the client used in ConnectionWorker #1933
Conversation
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
@@ -206,7 +205,9 @@ private StreamWriter(Builder builder) throws IOException { | |||
"Trying to enable connection pool in non-default stream."); | |||
} | |||
|
|||
BigQueryWriteClient client = getBigQueryWriteClient(builder); | |||
// We need a client to perform some getWriteStream calls. | |||
BigQueryWriteClient client = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need to create another client here if the passed in client is null?
we won't use the newly created client?
Turned out dataflow is using a connection while they might close the externally passed in client. Resulting in a non-recoverable UNAVAILABLE error.