[
https://issues.apache.org/jira/browse/JENA-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134499#comment-16134499
]
ASF GitHub Bot commented on JENA-1381:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/274
I'm not that worried about this case. (Although I would actually have fewer
special graph names and more types, but that's just my taste; I'm not arguing
that we should change that now.) It was more your first remark about "Else,
we'd end up with `Optional<Node>` all over the place" and the fact that I don't
feel like we have a clear way to make any changes at all to the core SPI and
API. This (PR) isn't really the right place for the larger discussion-- I'll
take it to dev@.
> 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)
