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
At the moment we have the problem that some nodes cannot be updated because they do not have the latest schema version.
The nodes are of the schema ‘KnowledgeArticle’. The nodes that work correctly are on version 32.0. The nodes that do not work are still on version 28.0.
In the appendix you will find the history of the schema migration jobs as well as the schema definitions of the different versions. All jobs are in COMPLETED status.
We then tried to start a manual schema migration ({{mesh-url}}/api/v2/:project/branches/:branchUuid/migrateSchemas).
This then led to a NullPointerException, please see the attachment.
In my opinion, this is a bug in the schema migration handling.
What can we do so that the nodes that exist in schema version 28.0 are migrated correctly to schema version 32.0?
Hello everyone,
At the moment we have the problem that some nodes cannot be updated because they do not have the latest schema version.
The nodes are of the schema ‘KnowledgeArticle’. The nodes that work correctly are on version 32.0. The nodes that do not work are still on version 28.0.
In the appendix you will find the history of the schema migration jobs as well as the schema definitions of the different versions. All jobs are in COMPLETED status.
We then tried to start a manual schema migration ({{mesh-url}}/api/v2/:project/branches/:branchUuid/migrateSchemas).
This then led to a NullPointerException, please see the attachment.
In my opinion, this is a bug in the schema migration handling.
Thank you very much.
Greetings,
Giuseppe
knowledgeArticleSchema32v.json
knowledgeArticleSchema29v.json
knowledgeArticleSchema28v.json
knowledgeArticleJobs.json
migrationSchemaException.txt
The text was updated successfully, but these errors were encountered: