commit | 3f57890fb8ba5b8de63dd9bf0dbe3abb088be20c | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Mon Jun 12 11:44:32 2017 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Tue Aug 08 14:17:18 2017 +0200 |
tree | a67876c8b375da70010ed471ad5023e255bc82d7 | |
parent | 3441f652d13c3341041087253054ca5b926f90d3 [diff] |
Remove usage of AccountByEmailCache With change I1c24da1378 there is a new Emails class that allows looking up accounts by email. To find accounts by email it gets external IDs by email from the ExternalIdCache and extracts the account IDs from the external IDs. This is exactly what AccountByEmailCacheImpl.Loader was doing. In addition the Emails class does an index lookup to also find accounts by preferred email (see commit message of change I1c24da1378 for an explanation of why this is needed). Adapt all code to use the new Emails class instead of the AccountByEmailCache. Looking up accounts by email via the ExternalIdCache means that the SHA1 of the refs/meta/external-ids branch is read on each lookup (to verify that the cache is up to date). To avoid reading the SHA1 of the refs/meta/external-ids branch multiple times when looking up accounts by email in a loop the Emails class offers a method that can lookup accounts for several emails at once. This method is currently not used by Gerrit core, but plugins may need it (e.g. the find-owners plugin). When emails are changed the ExternalIdCache is automatically evicted since it detects when the refs/meta/external-ids branch was updated, hence manual cache eviction for this cache is not needed. Accounts are also reindexed if the preferred email is changed so that looking up accounts by preferred email via the account index always returns up-to-date results. The AccountByEmailCache is only removed in the follow-up change. This allows Google to adapt internal code to use the new API before the AccountByEmailCache is dropped. Change-Id: I991d21b1acc11025a23504655b5a2c4fea795acf Signed-off-by: Edwin Kempin <ekempin@google.com>
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.