| commit | 0648b5f9c6001ea1e3ab5507dd84959e3662979c | [log] [tgz] |
|---|---|---|
| author | Thomas Draebing <thomas.draebing@sap.com> | Fri Sep 16 09:25:55 2022 +0200 |
| committer | Saša Živkov <sasa.zivkov@sap.com> | Fri Sep 30 11:30:48 2022 +0200 |
| tree | fe834865df9538cc3a0d9d1900c326fa78f57303 | |
| parent | 276e8081b16006b88b2f1950f5c2beda3cf9222a [diff] |
Truncate commit message stored in FIELD_MESSAGE_EXACT index field Reindexing failed for changes with very long commit messages. This issue started to occur after introduction of the changes index V77 in Ic33c935f. Lucene has a limit on the number of bytes that can be contained in a field. Since the whole commit message was stored and there is no limit on the size of the commit message, the reindex could fail. Now the commit message will be truncated, if it is too long (longer than 32766 bytes). This should not require to create a new schema version, since it does not affect existing entries, but will just allow additional entries, which previously failed to be added. The downside of truncation is, that using regex to search within the commit message will only work for the beginning of the commit message. This should be acceptable however, since the number of changes with such long commit messages will be very small and full text search will still work. It would be desirable to make the max term length configurable, since different index implementations might have different limitations. However, this would require a considerable effort. Such a change is likely not suitable for a stable-branch. Further, the gain would be small, since almost all commit messages should fit into the current limit. Release-Notes: Regex Search Operator: trim long commit messages in index Bug: Issue 16043 Change-Id: Ic9f6185806d3decc171843a65afabe5c39a94435
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.