internal/bigquery: do not update schema if it has not changed

Even if the schema has not changed, updating it counts as a patch
operation that contributes to the table metadata update quota. We are
seeing dozens of thousands of error logs with exceeded quota. They are
currently not manifesting as actual errors in the pipeline (they are
just logged by bigquery services), but the official documentation
suggests they should. Either way, this CL tries to cut this at its root
by updating table only if the new schema is not the same as the old one.

Change-Id: I94b11c8fd3e12ca2c3649fc5339220f01441d28d
Run-TryBot: Zvonimir Pavlinovic <>
TryBot-Result: Gopher Robot <>
Reviewed-by: Jonathan Amsterdam <>
1 file changed
tree: b1f7ec5c5fad930e4f46f0d525f9609f60403887
  1. cmd/
  2. deploy/
  3. devtools/
  4. internal/
  5. terraform/
  6. .dockerignore
  7. .gitignore
  8. all_test.go
  9. checks.bash
  10. config.json.commented
  12. go.mod
  13. go.sum
  15. Makefile
  18. tools.go


This repository contains code that serves

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the time repository is located at Prefix your issue with “x/pkgsite-metrics:” in the subject line, so it is easy to find.