[
https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712135#comment-16712135
]
ASF GitHub Bot commented on JENA-1645:
--------------------------------------
Github user xristy commented on the issue:
https://github.com/apache/jena/pull/503
I merged PR 503 into local master and pushed to
https://git-wip-us.apache.org/repos/asf/jena.git with message:
JEAN-1645 Merge commit 'refs/pull/503/head' of
https://github.com/apache/jena. This closes #503
owing to the misspelling of JENA as JEAN programmatic resolving of the
issue and closing of the PR has not happened. The code changes are in the ASF
jena repo as expected.
> Poor performance with full text search (Lucene)
> -----------------------------------------------
>
> Key: JENA-1645
> URL: https://issues.apache.org/jira/browse/JENA-1645
> Project: Apache Jena
> Issue Type: Question
> Components: Jena
> Affects Versions: Jena 3.9.0
> Reporter: Vasyl Danyliuk
> Priority: Major
>
> Situation: half of a million of an indexed by Lucene documents(emails
> actually), searching for emails by sender/receiver and some text.
> If to put text filter in the start of SPARQL query it executes once but in a
> case of very common words here are a lot of results(100 000+) that leads to
> poor performance, limiting results count may and up with missed results.
> If to put text search as the last condition it executes once per each already
> found subject. That's completely OK but text search completely ignores
> subject URI.
> I found two methods in TextQueryPF class: variableSubject(...) for the first
> case, and concreteSubject(...) for the second one.
> The question is: why can't subject URI be used as a constraint in the text
> search?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
