[jira] [Created] (UNOMI-996) Migration from Unomi 3.0 stops before it finishes

["Serge Huber (Jira)" <ji...@apache.org>]

Serge Huber created UNOMI-996:
---------------------------------

             Summary: Migration from Unomi 3.0 stops before it finishes
                 Key: UNOMI-996
                 URL: https://issues.apache.org/jira/browse/UNOMI-996
             Project: Apache Unomi
          Issue Type: Bug
    Affects Versions: unomi-4.0.0
            Reporter: Serge Huber
             Fix For: unomi-4.0.0


h3. Summary

When you follow the 3.0 to 4.0 migration guide on real 3.0 data, the migration stops almost at once with the message "no mapping found in bundles".

The guide asks you to run the migration before Unomi is started. At that point, Unomi has not yet loaded the parts that contain the index definitions the migration needs. In 3.0 these parts were loaded at boot, so the same steps worked.

A second problem stops the migration later. Some indices have no known definition, and the migration stops on them instead of handling them. Every 3.0 cluster has one of these, the cluster node index. Clusters that saved a Salesforce connector configuration have another.

The goal of this ticket is that the documented steps migrate a real 3.0 data set to the end.

h3. Ways to explore
* Make the index definitions available to the migration command itself, rather than starting all Unomi services first. Unomi should not answer requests before the migration has finished.
* Give the cluster node index a known definition. For other unknown indices, copy their current definition and assign their documents to the "default" tenant, like other site data. Never assign them to "system", and never leave documents without a tenant.
* If a manual step is still needed, add it to the migration guide.

h3. How to test

Start from a Unomi 3.0.1 data set that includes the cluster node index and a Salesforce connector configuration. Follow the migration guide step by step. The migration must finish with no error.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)