Commit 34a5a6f7 authored by Gradl, Tobias's avatar Gradl, Tobias
Browse files

Workaround for nulled analyzer config implemented

parent 62b6e824
Pipeline #15911 passed with stages
in 5 minutes and 26 seconds
......@@ -223,17 +223,15 @@ public class DmeSyncService extends BaseSyncService<ExtendedDatamodelContainer,
putMapping = true;
} 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) {
/* 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
*/
datamodel.setAnalyzerFieldMap(existDatamodel.getAnalyzerFieldMap());
}
}
datamodelService.saveOrUpdate(datamodel);
......
Markdown is supported
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