Add changelog and change kv migration version in docs (#4345)

treeverse · Oct 9, 2022 · 220cf50 · 220cf50
1 parent 447c5e9
commit 220cf50
Show file tree

Hide file tree

Showing 3 changed files with 17 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,18 @@
 # Changelog
 
+## v0.80.2 - 2022-10-09
+
+This version fixes kv migration bug in 0.80.1. If you already migrated to kv successfully,
+you can skip this version.
+
+This release requires running database migration.
+The lakeFS service will not run if the migration version isn't compatible with the binary.
+Before running the new version you will be required to run migrate, with the new version.
+Please refer to this [upgrade documentation](https://docs.lakefs.io/reference/upgrade.html##lakefs-0800-or-greater-kv-migration) for more information on the specific migration to KV
+
+Bug fix:
+- Fix multiparts KV migration for null content-type (#4343)
+
 ## v0.83.2
 
 What's new:

diff --git a/docs/reference/upgrade.md b/docs/reference/upgrade.md
@@ -17,9 +17,9 @@ If you're upgrading, check whether the [release](https://github.com/treeverse/la
 
 ### lakeFS 0.80.0 or greater (KV Migration)
 
-Starting with version 0.80.0, lakeFS has transitioned from using a PostgreSQL based database implementation to a Key-Value datastore interface supporting
+Starting with version 0.80.2, lakeFS has transitioned from using a PostgreSQL based database implementation to a Key-Value datastore interface supporting
 multiple database implementations. More information can be found [here](https://github.com/treeverse/lakeFS/blob/master/design/accepted/metadata_kv/index.md).  
-Users upgrading from a previous version of lakeFS must pass through the KV migration version (0.80.0) before upgrading to newer versions of lakeFS.
+Users upgrading from a previous version of lakeFS must pass through the KV migration version (0.80.2) before upgrading to newer versions of lakeFS.
 
 > **IMPORTANT: Pre Migrate Requirements**  
 > * **Users using OS environment variables for database configuration must define the `connection_string` explicitly or as environment variable before proceeding with the migration.**  
@@ -50,7 +50,7 @@ For each lakeFS instance currently running with the database
    ```
 
 2. Stop all lakeFS instances
-3. Using the `lakefs` binary for the new version (0.80.0), run the following:
+3. Using the `lakefs` binary for the new version (0.80.2), run the following:
 
    ```bash
    lakefs migrate up

diff --git a/docs/understand/kv-in-a-nutshell.md b/docs/understand/kv-in-a-nutshell.md
@@ -11,7 +11,7 @@ has_children: false
 
 {% include toc.html %}
 
-Starting at version 0.80.0, lakeFS abandoned the tight coupling to [PostgreSQL](https://en.wikipedia.org/wiki/PostgreSQL) and moved all database operations to work over [Key-Value Store](https://en.wikipedia.org/wiki/Key%E2%80%93value_database)
+Starting at version 0.80.2, lakeFS abandoned the tight coupling to [PostgreSQL](https://en.wikipedia.org/wiki/PostgreSQL) and moved all database operations to work over [Key-Value Store](https://en.wikipedia.org/wiki/Key%E2%80%93value_database)
 
 While SQL databases, and Postgres among them, have their obvious advantages, we felt that the tight coupling to Postgres is limiting our users and so, lakeFS with Key Value Store is introduced.
 Our KV Store implements a generic interface, with methods for `Get`, `Set`, `Compare-and-Set`, `Delete` and `Scan`. Each entry is represented by a [`partition`, `key`, `value`] triplet. All these fields are generic byte-array, and the using module has maximal flexibility on the format to use for each field