Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
30.0.1
-
-
CP: sprint 90
-
2
-
Core: Platform
Description
Overview:
Upgrading a module to RMB >= v30.0.0 fails when schema.json contains a foreignKey entry with targetPath (without fieldName).
Error log:
2020-06-02T16:08:06,982 INFO [vert.x-eventloop-thread-2] LogUtil 127.0.0.1:33566 POST /_/tenant null HTTP_1_1 201 0 254 tid=new_tenant Created 2020-06-02T16:08:06,985 INFO [main ] TenantSampleDataTest -- upgrade the tenant with sample data, so that it will be inserted now -- 2020-06-02T16:08:06,985 INFO [main ] TenantSampleDataTest upgrading Module with sample 2020-06-02T16:08:06,997 INFO [vert.x-worker-thread-7 ] TenantReferenceAPI postTenant 2020-06-02T16:08:06,998 INFO [vert.x-worker-thread-7 ] TenantAPI sending... postTenant for new_tenant 2020-06-02T16:08:07,012 ERROR [vert.x-eventloop-thread-2] TenantAPI null java.lang.NullPointerException: null at org.folio.rest.persist.ddlgen.SchemaMaker.lambda$3(SchemaMaker.java:159) ~[domain-models-runtime-30.0.1.jar:?]
This is caused by SchemaMaker.java line 159
oldForeignKey.getFieldName().equals(newForeignKey.getFieldName())
because oldForeignKey.getFieldName() is null when oldForeignKey uses targetPath.
Task:
Properly handle targetPath where fieldName is null.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODFISTO-111
Final verification migration scripts before release Q2 2020
-
- Closed
-
-
MODINVOSTO-67
Final verification migration scripts before release Q2 2020
-
- Closed
-
-
MODORDSTOR-152
Final verification migration scripts before release Q2 2020
-
- Closed
-
- relates to
-
RMB-569 Drop fromModuleVersion and tOps from table section, use schema.json comparison instead
-
- Closed
-