This is an automated email from the ASF dual-hosted git repository. meonkeys pushed a commit to branch release-doc-fixes in repository https://gitbox.apache.org/repos/asf/fineract.git
commit a3c80138f2c12e46de739845c5701f411f1e8df2 Author: Adam Monsen <[email protected]> AuthorDate: Sun Jul 27 20:27:25 2025 -0700 fix broken enumerated list resolves these warnings seen with, e.g.: `gradle --info doc` Jul 27, 2025 8:26:48 PM uri:classloader:/gems/asciidoctor-2.0.10/lib/asciidoctor/parser.rb parse_list_item WARNING: chapters/architecture/persistence.adoc: line 104: list item index: expected 1, got 2 Jul 27, 2025 8:26:48 PM uri:classloader:/gems/asciidoctor-2.0.10/lib/asciidoctor/parser.rb parse_list WARNING: chapters/architecture/persistence.adoc: line 110: list item index: expected 1, got 3 --- .../src/docs/en/chapters/architecture/persistence.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/fineract-doc/src/docs/en/chapters/architecture/persistence.adoc b/fineract-doc/src/docs/en/chapters/architecture/persistence.adoc index 75e816d560..067b307e4b 100644 --- a/fineract-doc/src/docs/en/chapters/architecture/persistence.adoc +++ b/fineract-doc/src/docs/en/chapters/architecture/persistence.adoc @@ -85,38 +85,38 @@ The switch from Flyway (1.6.x) to Liquibase (1.7.x) was planned to be as smooth === Troubleshooting 1. During upgrade from Fineract 1.5.0 to 1.6.0, Liquibase fails - ++ After dropping the flyway migrations table (schema_version), Liquibase runs its own migrations which fails (in recreating tables which already exist) because we are aiming to re-use DB with existing data from Fineract 1.5.0. - ++ Solution: The latest release version (1.6.0) doesn't have Liquibase at all, it still runs Flyway migrations. Only the develop branch (later to be 1.7.0) got switched to Liquibase. Do not pull the develop before upgrading your instance. - ++ Make sure first you upgrade your instance (aka database schema with Fineract 1.6.0). Then upgrade with the current develop branch. Check if some migration scripts did not run which led to some operations failing due to slight differences in schema. Try with running the missing migrations manually. - ++ Note: develop is considered unstable until released. 2. Upgrading database from MySQL 5.7 as advised to Maria DB 10.6, fails. If we use data from version 18.03.01 it fails to migrate the data. If we use databases running on 1.5.0 release it completes the startup but the system login fails. - ++ Solution: A database upgrade is separate thing to take care of. 3. We are getting `ScehmaUpgradeNeededException: Make sure to upgrade to Fineract 1.6 first and then to a newer version` error while upgrading to `tag 1.6`. - ++ 1.6 version shouldn't include Liquibase. It will only be released after 1.6. Make sure Liquibase is dropping `schema_version` table, as there is no Flyway it is not required. Drop Flyway and use Liquibase for both migrations and database independence. In case, if you still get errors, you can use git SHA `746c589a6e809b33d68c0596930fcaa7338d5270` and Flyway migration will be done to the latest. - ++ ``` TENANT_LATEST_FLYWAY_VERSION = 392; TENANT_LATEST_FLYWAY_SCRIPT_NAME =
