Commit 62b6e824 authored by Gradl, Tobias's avatar Gradl, Tobias
Browse files

Workaround for nulled analyzer config implemented

parent 198b2dbc
......@@ -16,7 +16,7 @@ plugins {
group = 'eu.dariah.de.minfba'
version = '1.19.4-SNAPSHOT'
version = '1.19.5-SNAPSHOT'
description = 'DARIAH-DE Search Commons'
sourceCompatibility = '1.8'
......
......@@ -224,6 +224,17 @@ public class DmeSyncService extends BaseSyncService<ExtendedDatamodelContainer,
} else if (indexable && datamodel.getIndexName()==null) {
datamodel.setIndexName(existDatamodel.getIndexName());
}
/* TODO: This needs some rework
* 1. Skipping this always sets analyzerFieldMap to null, it is only rebuilt if the mapping is updated to include a new configured element
* 2. Leaving this means that the analyzer config cannot be rebuild even when manually recreating the index, which can lead to problems
*
* => analyzerFieldMap should not be saved with the datamodel as coming from the DME in the future to prevent all this
*/
if (existDatamodel.getAnalyzerFieldMap()!=null) {
datamodel.setAnalyzerFieldMap(existDatamodel.getAnalyzerFieldMap());
}
datamodelService.saveOrUpdate(datamodel);
// New models -> create index/mapping automatically if configured
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment