Original issue when running the updater:
Bryan: It seems likely that this is about an illegal value (in the specific UPDATE request). However, it also seems that the option for xsd validation might not be consistently respected. Two different issues. Finally, we need better error messages for rejected values.
Root cause details:
After SPARQL Parsers refactoring (https://jira.blazegraph.com/browse/BLZG-1176), this portion of SPARQL Update processing does not have any access to journal and namespace configurations.
Also, a typed literal consists of a lexical form and a datatype, which restricts 'value space' and 'lexical space' of the corresponding values according to XML Schema Datatypes, and does not seem to be allowing an empty string as a lexical form.
- allow invalid literals in ASTDeferredIVResolutionInitializer.getBigdataValue() and provide FullyInlineTypedLiteralIV with an empty value without calling IVUtility.decode() to avoid NumberFormatException
- check for INLINE_XSD_DATATYPE_LITERALS and REJECT_INVALID_XSD_VALUES while executing an update and fail if invalid literals should be rejected.
- handle SPARQL type error during query evaluation, providing comprehensible error message.