Google Git
Sign in
gerrit / gerrit / 192dfd7bc6dc9b1d363180d1fbacff743f2412c9
commit192dfd7bc6dc9b1d363180d1fbacff743f2412c9[log] [tgz]
authorInderjot Kaur Ratol <inderjot.kaur.ratol@ericsson.com>Tue May 01 13:31:23 2018 -0400
committerDavid Pursehouse <dpursehouse@collab.net>Wed May 02 10:16:51 2018 +0900
tree888b6e7e5d4333a6dd1ac40e21bf1b9b2549e784
parent2bca209ef127ed3c39532d77a2be7858c2263952 [diff]
Fix the online index for changes when upgrading ES gerrit site

Previously, when using ElasticSearch as main index engine and
upgrading the gerrit site from 2.14 to 2.15, the changes were not
visible in the UI even when OnlineIndexer logs showed that indexing
was successful.

Reason: After migration, new indices were never created with the custom
mappings and elasticsearch created the default mappings with the
standard fields used in the indices. This resulted in a mismatch between
the mapping types and therefore changes were not visible in the UI.

For example:

The "changes" index in gerrit use two types of mappings - "open_changes"
and "closed_changes". When no index was created by gerrit and
onlineIndexer was called while running gerrit with the migrated site,
elasticsearch created only "open_changes" mapping type resulting in
conflicts between two different versions of the same indices.

This change resolves the inconsistencies between offline and online
reindex by deleting all the previously existing indices and creating the
new ones.

Bug: Issue 8806
Change-Id: I51ee5bfeb2a154630955b3c94b78fda7d050610d
1 file changed
tree: 888b6e7e5d4333a6dd1ac40e21bf1b9b2549e784
  1. .settings/
  2. contrib/
  3. Documentation/
  4. gerrit-acceptance-framework/
  5. gerrit-acceptance-tests/
  6. gerrit-cache-h2/
  7. gerrit-common/
  8. gerrit-elasticsearch/
  9. gerrit-extension-api/
  10. gerrit-gpg/
  11. gerrit-gwtdebug/
  12. gerrit-gwtexpui/
  13. gerrit-gwtui/
  14. gerrit-gwtui-common/
  15. gerrit-httpd/
  16. gerrit-index/
  17. gerrit-launcher/
  18. gerrit-lucene/
  19. gerrit-main/
  20. gerrit-oauth/
  21. gerrit-openid/
  22. gerrit-patch-commonsnet/
  23. gerrit-patch-jgit/
  24. gerrit-pgm/
  25. gerrit-plugin-api/
  26. gerrit-plugin-gwtui/
  27. gerrit-prettify/
  28. gerrit-reviewdb/
  29. gerrit-server/
  30. gerrit-sshd/
  31. gerrit-test-util/
  32. gerrit-util-cli/
  33. gerrit-util-http/
  34. gerrit-util-ssl/
  35. gerrit-war/
  36. lib/
  37. plugins/
  38. polygerrit-ui/
  39. ReleaseNotes/
  40. tools/
  41. website/
  42. .bazelproject
  43. .editorconfig
  44. .git-blame-ignore-revs
  45. .gitignore
  46. .gitmodules
  47. .mailmap
  48. .pydevproject
  49. BUILD
  50. COPYING
  51. INSTALL
  52. README.md
  53. SUBMITTING_PATCHES
  54. version.bzl
  55. WORKSPACE
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recursive https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

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.