[
https://issues.apache.org/jira/browse/JENA-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136775#comment-15136775
]
Rob Vesse commented on JENA-1133:
---------------------------------
This relates to an internal implementation detail,
{{urn:x-arq:DefaultGraphNode}} is intended for internal use whereas
{{urn:x-arq:DefaultGraph}} is intended for user facing use
I see two possible fixes:
# Changing the indexing logic to use {{Quad.isDefaultGraph(Node)}} and
normalising to one form or another. This will require some existing text
indexes to be rebuilt.
# Changing the search logic to use {{Quad.isDefaultGraph(Node)}} and then
searching for both the possible default graph node URIs
Note that it may also be possible though unlikely to see
{{urn:x-arq:UnionGraph}} in indexing and/or search which may also warrant some
special handling
> default graph triples incorrectly indexed by jena.textindexer
> -------------------------------------------------------------
>
> Key: JENA-1133
> URL: https://issues.apache.org/jira/browse/JENA-1133
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
> Reporter: Osma Suominen
>
> Reported by Joachim Neubert on users@jena:
> https://mail-archives.apache.org/mod_mbox/jena-users/201602.mbox/%3C4E3518D35BC4E14B802A8CAE0E8819CF747543EF%40lhun.zbw-nett.zbw-kiel.de%3E
> When the jena-text index is configured with graphField, triples in the
> default graph are indexed with a different graph URI than otherwise (e.g.
> using HTTP Graph Store Protocol in Fuseki): the graph URI is
> "urn:x-arq:DefaultGraph" instead of "urn:x-arq:DefaultGraphNode".
> This causes text queries for the default graph to not return results from
> triples loaded this way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
