Google Git
Sign in
chromium / infra / luci / luci-go / 06efb29314fa0641ff2176ffb926f85e9c7ed05f
commit06efb29314fa0641ff2176ffb926f85e9c7ed05f[log] [tgz]
authorBeining Chen <beining@google.com>Tue May 20 04:33:56 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 20 04:33:56 2025
tree80c7b3f5bf63475fab412efd5bfcf7cfa903ab35
parent7004c7de06d4346ce10cbba90df138839fdda37c [diff]
[common][analysis] Add BigQuery Schema Option for Default Values

This change introduces a new option to specify default values within the BigQuery schema proto definition.

Motivation:
* Prevent Overrides: The primary goal is to safeguard against unintentional removal of manually added default values in BigQuery table schemas. While the current schemaaplyer.go does not override existing field default values, this behavior isn't guaranteed indefinitely.
* Ensure Consistency: By defining the default value in the codebase, we improve the consistency between our schema definitions and the actual state of the BigQuery tables.

Further details regarding this default value option can be found in common/bq/pb/options.proto

Also, add default value option to insert_time in AntsTestResultRow.

Bug: b:408309587
Change-Id: I820c3ee46de0387b359d870a32c5b6753cf353d0
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6539369
Reviewed-by: Patrick Meiring <meiring@google.com>
Commit-Queue: Beining Chen <beining@google.com>
7 files changed
tree: 80c7b3f5bf63475fab412efd5bfcf7cfa903ab35
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. cipkg/
  11. client/
  12. common/
  13. config/
  14. config_service/
  15. cv/
  16. deploy/
  17. examples/
  18. gae/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. led/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. luciexe/
  28. mailer/
  29. milo/
  30. mmutex/
  31. provenance/
  32. recipes_py/
  33. resultdb/
  34. scheduler/
  35. scripts/
  36. server/
  37. source_index/
  38. standalone/
  39. starlark/
  40. swarming/
  41. teams/
  42. third_party/
  43. tokenserver/
  44. tools/
  45. tree_status/
  46. vpython/
  47. web/
  48. .gitallowed
  49. .gitignore
  50. .go-lintable
  51. AUTHORS
  52. codereview.settings
  53. CONTRIBUTING.md
  54. CONTRIBUTORS
  55. go.mod
  56. go.sum
  57. LICENSE
  58. OWNERS
  59. PRESUBMIT.py
  60. README.md
  61. staticcheck.conf
  62. tools.go
  63. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoReference

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

It is now possible to directly install tools with go install:

go install go.chromium.org/luci/auth/client/cmd/...@latest
go install go.chromium.org/luci/buildbucket/cmd/...@latest
go install go.chromium.org/luci/cipd/client/cmd/...@latest
go install go.chromium.org/luci/client/cmd/...@latest
go install go.chromium.org/luci/cv/cmd/...@latest
go install go.chromium.org/luci/gce/cmd/...@latest
go install go.chromium.org/luci/grpc/cmd/...@latest
go install go.chromium.org/luci/logdog/client/cmd/...@latest
go install go.chromium.org/luci/luci_notify/cmd/...@latest
go install go.chromium.org/luci/lucicfg/cmd/...@latest
go install go.chromium.org/luci/luciexe/legacy/cmd/...@latest
go install go.chromium.org/luci/mailer/cmd/...@latest
go install go.chromium.org/luci/mmutex/cmd/...@latest
go install go.chromium.org/luci/resultdb/cmd/...@latest
go install go.chromium.org/luci/server/cmd/...@latest
go install go.chromium.org/luci/swarming/cmd/...@latest
go install go.chromium.org/luci/tokenserver/cmd/...@latest
go install go.chromium.org/luci/tools/cmd/...@latest

Contributing

Contributing uses the same flow as Chromium contributions.