diff options
| author | Edwin Kempin <edwin.kempin@sap.com> | 2012-10-18 13:01:12 +0200 |
|---|---|---|
| committer | Edwin Kempin <edwin.kempin@sap.com> | 2012-10-18 13:10:20 +0200 |
| commit | e3aa0f541fe2b1f151abdb91aeeb6d85f40837e8 (patch) | |
| tree | 671758420f4f2260ab944f796da0fb0f5f7608f8 | |
| parent | 721131a17d0d7f20efc8e484407953e8b7e07cca (diff) | |
Explain warning for schema version 68 in Gerrit 2.5 release notes
The migration for schema version 68 may result in a warning. Explain
in the Gerrit 2.5 release notes why this warning may happen and in
which case it can be safely ignored.
Change-Id: I5cdb392e5e3b7389818ad0d57bc1390d3ab408f6
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
| -rw-r--r-- | ReleaseNotes/ReleaseNotes-2.5.txt | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/ReleaseNotes/ReleaseNotes-2.5.txt b/ReleaseNotes/ReleaseNotes-2.5.txt index 47828feb6c..b545f7b635 100644 --- a/ReleaseNotes/ReleaseNotes-2.5.txt +++ b/ReleaseNotes/ReleaseNotes-2.5.txt @@ -21,6 +21,33 @@ Schema Change a later 2.1.x version), and then to 2.5.x. If you are upgrading from 2.2.x.x or newer, you may ignore this warning and upgrade directly to 2.5.x. +Warning on upgrade to schema version 68 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The migration to schema version 68, may result in a warning, which can +be ignored when running init in the interactive mode. + +E.g. this warning may look like this: + +---- +Upgrading database schema from version 67 to 68 ... +warning: Cannot create index for submodule subscriptions +Duplicate key name 'submodule_subscriptions_access_bySubscription' +Ignore warning and proceed with schema upgrade [y/N]? +---- + +This migration is creating an index for the +link:../Documentation/user-submodules.html[submodule feature] in +Gerrit. When the submodule feature was introduced the index was only +created when a new site was initialized, but not when Gerrit was +upgraded. This migration tries to create the index, but it will only +succeed if the index does not exist yet. If the index exists already, +the creation of the index will fail. There was no database independent +way to detect this case and this is why this migration leaves it to the +user to decide if a failure should be ignored or not. If from the error +message you can see that the migration failed because the index exists +already (as in the example above), you can safely ignore this warning. + Upgrade Warnings ---------------- |