docs(sample): Fix PERMISSION_DENIED in WriteCommittedStream
#1248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
product-auto-label
bot
added
the
api: bigquerystorage
google-cla
bot
added
the
cla: yes
…tedStream` The sample yields a `PERMISSION_DENIED` error if we pass the `client` even if the regions are compatible and the authenticated gcloud agent/service has the required permissions. More details on: https://issuetracker.google.com/issues/196338290
bphenriques
changed the title
PERMISSION_DENIED in WriteCommittedStreamPERMISSION_DENIED in WriteCommittedStream
stephaniewang526
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
|
could you share the buganizer ticket related to this please? |
product-auto-label
bot
added
the
samples
|
I only have access to https://issuetracker.google.com/issues/196338290 Another ticket (where the resolution was proposed) was created in my behalf by a colleague of mine, therefore I do not have permissions. I only have access to the email thread which says that it is case #28707078. |
stephaniewang526
approved these changes
Aug 23, 2021
gcf-merge-on-green bot
pushed a commit
that referenced
this issue
Aug 24, 2021
🤖 I have created a release \*beep\* \*boop\* --- ## [2.1.0](https://www.github.com/googleapis/java-bigquerystorage/compare/v2.0.4...v2.1.0) (2021-08-24) ### Features * retry certain RESOURCE_EXHAUSTED errors observed during ReadRows and report retry attempts ([#1257](https://www.github.com/googleapis/java-bigquerystorage/issues/1257)) ([d56e1ca](https://www.github.com/googleapis/java-bigquerystorage/commit/d56e1caf91297d7c2e1e4a9ce1463c04e44619c0)) ### Documentation * **sample:** Remove `client` from `JsonStreamWriter` in `WriteCommittedStream` ([#1248](https://www.github.com/googleapis/java-bigquerystorage/issues/1248)) ([6d38bd5](https://www.github.com/googleapis/java-bigquerystorage/commit/6d38bd5e3ff383e55e852081bbea5807796f59dd)) ### Dependencies * update dependency com.google.cloud:google-cloud-shared-dependencies to v2.1.0 ([#1261](https://www.github.com/googleapis/java-bigquerystorage/issues/1261)) ([0edb25d](https://www.github.com/googleapis/java-bigquerystorage/commit/0edb25d4a55f5480d5717672f30b09e6433483b9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
See details in #1246 .
This is a suggestion from Google's support (Case#28707078) which I am documenting here in case others stumble upon this issue.
It is odd that passing the
clienttriggers the error therefore this PR only aims to fix the sample rather than working out the production code (which is still in PRE-GA so issues are expected). Feel free to close this PR if the production code is fixed instead in the meantime (which is preferable).Let me know if I need add more details on the issue. I omitted as the linked ticket includes the details.
Fixes #1246☕️
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:
[ ] Code coverage does not decrease (if any source code was changed)