You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Leigh Dodds (JIRA)" <ji...@apache.org> on 2013/04/17 17:19:16 UTC

[jira] [Created] (JENA-438) Fuseki can produce no query results with broken XML literal

Leigh Dodds created JENA-438:
--------------------------------

             Summary: Fuseki can produce no query results with broken XML literal
                 Key: JENA-438
                 URL: https://issues.apache.org/jira/browse/JENA-438
             Project: Apache Jena
          Issue Type: Bug
          Components: Fuseki
    Affects Versions: Jena 2.10.0
            Reporter: Leigh Dodds
            Priority: Minor


Whilst trying to track down some other odd behaviour (which may or may not be related!) I noticed that Fuseki reacts differently to TDB command-line when handling invalid XML literals.

Using Jena 2.10.0 and Fuseki 0.2.7-SNAPSHOT I indexed the following using tdbloader:

<http://example.org/resource> <http://example.org/predicate> "<broken>This is broken</yes>"^^<http://www.w3.org/1999/02/22-rdf-syntax-
ns#XMLLiteral>.

During processing riot gives me the following warning, but does add the triple to the index:

16:03:12 WARN  riot                 :: [line: 1, col: 62] Lexical form '<broken>This is broken</yes>' not valid for datatype http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral

Using tdbquery I can run SELECT * WHERE { ?s ?p ?o } and I get a single result, as expected.

If I mount the indexes in fuseki and run the same query then I get a JSON file with no bindings:

{
  "head": {
    "vars": [ "s" , "p" , "o" ]
  } ,
  "results": {
    "bindings": [
      
    ]
  }
}

DESCRIBE <http://example.org/resource> produces an empty document {}.

There are no warnings or errors in the Fuseki logs. So looks like fuseki is handling the query results differently to tdbquery which still returns the invalid data.




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira