This repository was archived by the owner on Feb 7, 2026. It is now read-only.
Conversation
stephenplusplus
approved these changes
Dec 27, 2018
Contributor
stephenplusplus
left a comment
There was a problem hiding this comment.
This is kind of weird. I would guess we enabled setMetadata by mistake for the Jobs API.
crwilcox
approved these changes
Dec 27, 2018
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.Suggestion cannot be applied right now. Please check back later.
BigQuery/Jobs API doesn't (no longer?) support PATCH method on jobs.
I'm not sure if it used to, @stephenplusplus, but the REST reference doesn't show a PATCH method.
When attempting to call Job.setMetadata, the promise rejects citing "Unable to parse JSON" because the server returned a 404 HTML response saying the method is not found.