Skip to content
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: split connection pool based on credential #2388

Merged
merged 2 commits into from Feb 2, 2024

Conversation

GaoleMeng
Copy link
Contributor

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕️

If you write sample code, please follow the samples format.

@GaoleMeng GaoleMeng requested a review from a team as a code owner January 31, 2024 00:19
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: bigquerystorage Issues related to the googleapis/java-bigquerystorage API. labels Jan 31, 2024
@@ -273,14 +278,18 @@ private StreamWriter(Builder builder) throws IOException {
}
}
this.location = location;
CredentialsProvider credentialsProvider = client.getSettings().getCredentialsProvider();
log.warning("The credentials gotten is " + credentialsProvider.getCredentials());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we printing this out?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrong debug log, removed

ConnectionPoolKey.create(location),
ConnectionPoolKey.create(
location,
credentialsProvider != null ? credentialsProvider.getCredentials() : null),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use a hash for the key instead? I am wondering if there could be a security concern here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to use hash

@GaoleMeng GaoleMeng added the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 1, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 1, 2024
@GaoleMeng GaoleMeng requested a review from a team as a code owner February 2, 2024 01:19
@GaoleMeng GaoleMeng added the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 2, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 2, 2024
@GaoleMeng GaoleMeng merged commit 08bc846 into googleapis:main Feb 2, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquerystorage Issues related to the googleapis/java-bigquerystorage API. size: m Pull request size is medium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants