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
On RecordsFactory, within the method "getRecords", there is a check to see if the given reference formulation found in the mapping file is actually supported by the mapper. In the case of a non-supported reference formulation found, the code logs an error and leaves the execution run without returning from the method or throwing a controlled error.
// Select the Record Factory based on the reference formulation. if (!referenceFormulationRecordFactoryMap.containsKey(referenceFormulation)) {
logger.error("Referenceformulation {} is unsupported!", referenceFormulation);
}
ReferenceFormulationRecordFactoryfactory = referenceFormulationRecordFactoryMap.get(referenceFormulation);
records = factory.getRecords(access, logicalSource, rmlStore);
Instead what happens is a factory is tried to be retrieved and use this reference, which leads to a NullPointerExcepcion that in turn gets propagated all the way up the Executor class. This happens between lines 138 and 142 of the class RecordsFactory. I have verified this error is still present on the development branch.
The text was updated successfully, but these errors were encountered:
On RecordsFactory, within the method "getRecords", there is a check to see if the given reference formulation found in the mapping file is actually supported by the mapper. In the case of a non-supported reference formulation found, the code logs an error and leaves the execution run without returning from the method or throwing a controlled error.
Instead what happens is a factory is tried to be retrieved and use this reference, which leads to a NullPointerExcepcion that in turn gets propagated all the way up the Executor class. This happens between lines 138 and 142 of the class RecordsFactory. I have verified this error is still present on the development branch.
The text was updated successfully, but these errors were encountered: