You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Fixes #...
14
14
-[ ] Automated tests have been added.
15
15
-[ ] If some tests cannot be automated, manual rigorous tests should be applied.
16
16
-[ ] ⚠️ If there is any change in the DB:
17
-
-[ ] Test that any impacted DB still works as expected after using `--experimental-dumpless-upgrade` on a DB created with the last released Meilisearch
17
+
-[ ] Test that any impacted DB still works as expected after using `--upgrade-db` on a DB created with the last released Meilisearch
18
18
-[ ] Test that during the upgrade, **search is still available** (artificially make the upgrade longer if needed)
19
19
-[ ] Set the `db change` label.
20
20
-[ ] If necessary, the feature have been tested in the Cloud production environment (with [prototypes](./documentation/prototypes.md)) and the Cloud UI is ready.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -238,7 +238,7 @@ This project uses GitHub Merge Queues that helps us manage pull requests merging
238
238
Before merging a PR, the maintainer should ensure the following requirements are met
239
239
- Automated tests have been added.
240
240
- If some tests cannot be automated, manual rigorous tests should be applied.
241
-
- ⚠️ If there is an change in the DB: it's mandatory to manually test the `--experimental-dumpless-upgrade` on a DB of the previous Meilisearch minor version (e.g. v1.13 for the v1.14 release).
241
+
- ⚠️ If there is an change in the DB: it's mandatory to manually test the `--upgrade-db` on a DB of the previous Meilisearch minor version (e.g. v1.13 for the v1.14 release).
242
242
- If necessary, the feature have been tested in the Cloud production environment (with [prototypes](./documentation/prototypes.md)) and the Cloud UI is ready.
243
243
- If necessary, the [documentation](https://github.com/meilisearch/documentation) related to the implemented feature in the PR is ready.
244
244
- If necessary, the [integrations](https://github.com/meilisearch/integration-guides) related to the implemented feature in the PR are ready.
Copy file name to clipboardExpand all lines: TESTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,9 +198,9 @@ In most cases, the change binary instruction will be used to update a database.
198
198
199
199
To properly test the dumpless upgrade, one should typically:
200
200
201
-
1. Open the database without processing the update task: Use a `binary` instruction to switch to the desired version, passing `--experimental-dumpless-upgrade` and `--experimental-max-number-of-batched-tasks=0` as extra CLI arguments
201
+
1. Open the database without processing the update task: Use a `binary` instruction to switch to the desired version, passing `--upgrade-db` and `--experimental-max-number-of-batched-tasks=0` as extra CLI arguments
202
202
2. Check that the search, stats and task queue still work.
203
-
3. Open the database and process the update task: Use a `binary` instruction to switch to the desired version, passing `--experimental-dumpless-upgrade` as the extra CLI argument. Use a `health` command to wait for the upgrade task to finish.
203
+
3. Open the database and process the update task: Use a `binary` instruction to switch to the desired version, passing `--upgrade-db` as the extra CLI argument. Use a `health` command to wait for the upgrade task to finish.
204
204
4. Check that the indexing, search, stats, and task queue still work.
205
205
206
206
```jsonc
@@ -223,7 +223,7 @@ To properly test the dumpless upgrade, one should typically:
223
223
"source":"build", // build the binary from the sources in the current git repository
224
224
"edition":"community",
225
225
"extraCliArgs": [
226
-
"--experimental-dumpless-upgrade", // allows to open with a newer MS
226
+
"--upgrade-db", // allows to open with a newer MS
227
227
"--experimental-max-number-of-batched-tasks=0"// prevent processing of the update task
228
228
]
229
229
}
@@ -238,7 +238,7 @@ To properly test the dumpless upgrade, one should typically:
238
238
"source":"build", // build the binary from the sources in the current git repository
239
239
"edition":"community",
240
240
"extraCliArgs": [
241
-
"--experimental-dumpless-upgrade"// allows to open with a newer MS
241
+
"--upgrade-db"// allows to open with a newer MS
242
242
// no `--experimental-max-number-of-batched-tasks=0`
Copy file name to clipboardExpand all lines: crates/index-scheduler/src/upgrade/mod.rs
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ pub fn upgrade_index_scheduler(
65
65
66
66
if initial_version < (1,12,0){
67
67
bail!(
68
-
"Database version {initial_major}.{initial_minor}.{initial_patch} is too old for the experimental dumpless upgrade feature. Please generate a dump using the v{initial_major}.{initial_minor}.{initial_patch} and import it in the v{target_major}.{target_minor}.{target_patch}",
68
+
"Database version {initial_major}.{initial_minor}.{initial_patch} is too old to be upgraded via `--upgrade-db`. Please generate a dump using the v{initial_major}.{initial_minor}.{initial_patch} and import it in the v{target_major}.{target_minor}.{target_patch}",
Copy file name to clipboardExpand all lines: crates/meilisearch-types/src/versioning.rs
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -81,13 +81,14 @@ pub enum VersionFileError {
81
81
MalformedVersionFile{context:String},
82
82
#[error(
83
83
"Your database version ({major}.{minor}.{patch}) is incompatible with your current engine version ({}).\n\
84
-
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.",
84
+
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.\n\
85
+
Alternatively, you can set the `--upgrade-db` flag (or the `MEILI_UPGRADE_DB` environment variable) to upgrade the database on startup.",
85
86
env!("CARGO_PKG_VERSION").to_string()
86
87
)]
87
88
VersionMismatch{major:u32,minor:u32,patch:u32},
88
89
#[error("Database version {major}.{minor}.{patch} is higher than the Meilisearch version {VERSION_MAJOR}.{VERSION_MINOR}.{VERSION_PATCH}. Downgrade is not supported")]
#[error("Database version {major}.{minor}.{patch} is too old for the experimental dumpless upgrade feature. Please generate a dump using the v{major}.{minor}.{patch} and import it in the v{VERSION_MAJOR}.{VERSION_MINOR}.{VERSION_PATCH}")]
91
+
#[error("Database version {major}.{minor}.{patch} is too old to be upgraded via `--upgrade-db`. Please generate a dump using the v{major}.{minor}.{patch} and import it in the v{VERSION_MAJOR}.{VERSION_MINOR}.{VERSION_PATCH}")]
0 commit comments