[ 
https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710649#comment-16710649
 ] 

ASF GitHub Bot commented on JENA-1645:
--------------------------------------

Github user osma commented on the issue:

    https://github.com/apache/jena/pull/503
  
    Looks good to me, based on a quick look at the diff. It took a while to 
figure out the way you use UnaryOperator but in the end it made sense.
    
    I'm currently travelling and haven't found time to actually run the code, 
but if it passes the existing unit tests and you're sure that they trigger the 
`concreteSubject` case, I'm fine with that.


> 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)

Reply via email to