| commit | 1deca310bcc5aadebe2010799bc3e4b4954890cc | [log] [tgz] |
|---|---|---|
| author | Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> | Tue Oct 11 16:37:29 2022 +0530 |
| committer | Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> | Mon Oct 31 22:01:18 2022 +0530 |
| tree | 007a67e30499fcceaf7a2f59a1878107483d861b | |
| parent | 0547b5dce1faad6f6f26952fd1aaed42974cbe3d [diff] |
Add HasCardinality interface which helps in defining a cardinality Before this change, cardinality of the IndexSource was always set to 10. This makes AndSource to choose IndexSource over other source almost always. Add a HasCardinality interface which can be used by all the predicates which implement IndexPredicate to set a cardinality. This helps AndSource to choose the right datasource. Unfortunately there are no operators which are datasources other than Index in the Core as of now. We at Qualcomm have a datasource operator in a plugin which takes a bug number and queries the bug tracker's DB for changes related to that bug number. Suppose this operator (say issue:123) returns around 15 changes. On a 3.4 test site against LUCENE which contains ~20K open changes, ~2.8M merged changes, the performance of, query "issue:123 status:open" when status:open is datasource: 2.1s, 2.1s, 2.1s when issue:123 is datasource: 0.07s, 0.07s, 0.07s query "issue:123 status:merged" when status:merged is datasource: 6m49s, 6m38s, 6m34s when issue:123 is datasource: 0.07s, 0.07s, 0.07s The cardinality of the predicates are restored from their previous values [1] and [2]. [1] https://gerrit-review.googlesource.com/c/gerrit/+/52078/8/gerrit-server/src/main/java/com/google/gerrit/server/query/change/SqlRewriterImpl.java#b576 [2] https://gerrit-review.googlesource.com/c/gerrit/+/63214 Release-Notes: AndSource chooses right datasource more often Change-Id: I802ab592d121b01dab9557da535f99411a1c7bc0
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 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 --recurse-submodules 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 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.