| commit | ff3e8320f43258c8199f68dbdf30e65112875264 | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Wed Jun 06 15:32:27 2018 -0400 |
| committer | David Pursehouse <dpursehouse@collab.net> | Sun Jun 10 13:11:33 2018 +0900 |
| tree | 32c727522a969a9374549ca4ab7d5419f8afaad8 | |
| parent | 370962bc72d443550a44d0c970c827d4c9b6b2b7 [diff] |
Elasticsearch: Add support for V6 / one index type Starting with ES 6.0.0, multiple mapping types within an index are no longer supported. Replace the open and closed changes index types with just one (type), for that V6 case. Name that single type '_doc', to help prepare V6 indices in Gerrit for a potential yet smoother migration to V7. -Choose such a name as it becomes the default one starting with V7. Consistently do so as well for the accounts and groups indices. Doing so has no negative impacts on the trivial way index types are used today. Refer to [1] for all these matters considered herein. Stick to the V2 index type names for the V5 case, as the latter does not support names starting with an underscore (such as '_doc' for V6+). Set the _type field only for Elasticsearch V2 and V5 usage, as it is deprecated starting with V6; cf. [2]. This is consistent with the above. These were the sole breaking changes between Elasticsearch V5 and V6 for the Gerrit ES client implementation. This change is also meant to preserve potentially existing V2 /default integrations or deployments. [1] https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html#_schedule_for_removal_of_mapping_types [2] https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-type-field.html Bug: Issue 9112 Change-Id: I92e6c74741976ef002aadded4e1915927aef46e5
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.