Closed jmaharramzade closed 4 years ago
Fixed; This was a bug in the datatype to sql-string mapping: Instead of "double" in the generated Spark SQL it was incorrectly "double precision" resulting in the catalyst parse exception with the not very helpful message.
I'll demonstrate the problem using the Sparqlify example: https://github.com/SANSA-Stack/SANSA-Examples/blob/develop/sansa-examples-spark/src/main/scala/net/sansa_stack/examples/spark/query/Sparqlify.scala.
Add a triple to src/main/resources/rdf.nt with an object of type XSD double. E.g., simply replace the following triple:
with:
Run the Sparqlify class in the server/endpoint mode pointing to the rdf.nt as input (--input src/main/resources/rdf.nt). Execute the simple
SELECT * WHERE {?s ?p ?o}
query in the browser. Observe the error in the server console.