[
https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713073#comment-16713073
]
ASF subversion and git services commented on JENA-1645:
-------------------------------------------------------
Commit 82121f9c52f4aac03d2121931326754d108938b2 in jena's branch
refs/heads/master from [~code-ferret]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=82121f9 ]
JENA-1645: This closes #503.
> 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
> Fix For: Jena 3.10.0
>
>
> 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)
