[ https://issues.apache.org/jira/browse/JENA-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134457#comment-16134457 ]
ASF GitHub Bot commented on JENA-1381: -------------------------------------- Github user afs commented on the issue: https://github.com/apache/jena/pull/274 That would be contrary to what every other place does. Having a name for the default graph unifies the design. Else, we'd end up with `Optional<Node>` all over the place, or compensatory code. > jena-text does not respect graph indexing in the text query cache > ----------------------------------------------------------------- > > Key: JENA-1381 > URL: https://issues.apache.org/jira/browse/JENA-1381 > Project: Apache Jena > Issue Type: Bug > Components: Text > Affects Versions: Jena 3.4.0 > Reporter: Andy Seaborne > Assignee: Andy Seaborne > Attachments: TextIndexReport.java > > > jena-text does not respect the graph setting when using the text query cache. > In the example attached, the dataset has two graphs; the first result is > used for the second text query. Depending on the order, either both text > queries are zero or both one hit when the right answer is zero, once and one, > once. > Note also the "graph" feature of jena-text only works with quad based > datasets (strictly, ones that use GraphView for their graphs). General > dataset do not. This is hidden in the pattern where there is a test triple > pattern that the literal is actually in the graph. -- This message was sent by Atlassian JIRA (v6.4.14#64029)