[
https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Code Ferret resolved JENA-1645.
-------------------------------
Resolution: Fixed
Fix Version/s: Jena 3.10.0
[PR #503|https://github.com/apache/jena/pull/503] is tested and merged via
[501d9f68d|https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=501d9f68d46e30ce5289b04dfba13f07bbf7d2d9]
.
> 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)
