Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.1
-
None
Description
Right now the following snippet of code contained within BaseRDFExtractor.java kills entire extractions. I propose to merely log the errors and continue with the extraction.
} catch (RDFParseException ex) { - throw new ExtractionException("Error while parsing RDF document.", ex, extractionResult); + LOG.error("Error while parsing RDF document.", ex, extractionResult); } }
The parsing strictness is inherited from the underlying semargl parsers which expect perfect syntax for input data... in the 'wild' however, this unfortunately is not realistic.
The solution is for us to log the Exception, issues, etc. and carry on with the extraction.
Patch coming up.
Attachments
Issue Links
- supercedes
-
ANY23-280 Refactor ContentExtractor to improve extraction flexibility
- Resolved
- links to