| commit | a0b57d4686c6f3553b689b97042aa223df87503d | [log] [tgz] |
|---|---|---|
| author | Julie Qiu <julie@golang.org> | Thu Sep 12 13:12:09 2019 -0400 |
| committer | Julie Qiu <julie@golang.org> | Fri Mar 27 16:46:43 2020 -0400 |
| tree | 16e6277ef93a5ec5c865a159b5c4d8e29266107b | |
| parent | 1dc556f8d212160e7674cfd698ef888d984372f8 [diff] |
internal/dcensus: add ViewByCodeRouteMethodLatencyDistribution dcensus.ViewByCodeRouteMethodLatencyDistribution is added, which provides a view for looking at the distribution of latency by status code, route, and method. Updates b/140245105 Updates b/132629518 Change-Id: If079c14b366db0d9493aa209bf31d4e430652a14 Reviewed-on: https://team-review.git.corp.google.com/c/golang/discovery/+/549683 CI-Result: Cloud Build <devtools-proctor-result-processor@system.gserviceaccount.com> Reviewed-by: Jonathan Amsterdam <jba@google.com>
Migrations are managed with the golang-migrate/migrate CLI tool.
To run all the migrations:
migrate -source file:migrations -database "postgres://localhost:5432/discovery-database?sslmode=disable" up
To create a new migration:
migrate create -ext sql -dir migrations -seq <title>
This creates two empty files in /migrations:
{version}_{title}.up.sql
{version}_{title}.down.sql
The two migration files are used to migrate “up” to the specified version from the previous version, and to migrate “down” to the previous version. See golang-migrate/migrate/MIGRATIONS.md for details.