[
https://issues.apache.org/jira/browse/JENA-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136779#comment-15136779
]
Osma Suominen commented on JENA-1133:
-------------------------------------
Thanks Rob, I was just going to implement your solution 1.
I don't like option 2, to me it doesn't make sense to have two different ways
of representing the default graph inside the text index and then having to
query them both.
UnionGraph is already handled as a special case for search. I don't see why it
would be needed for indexing.
> 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)
