[
https://issues.apache.org/jira/browse/JENA-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15619621#comment-15619621
]
Jean-Marc Vanel commented on JENA-1250:
---------------------------------------
It cannot be the reason pointed out by Osma in Lucene 5.5.3 guide:
"Instead, you should break out text into separate fields and use a different
analyzer for each field with PerFieldAnalyzerWrapper."
https://lucene.apache.org/core/5_5_3/MIGRATE.html
because the test fails the same way in Lucene 5.5.2 .
Moreover, it looks like Jena already breaks out text into separate fields and
uses PerFieldAnalyzerWrapper.
I'll try to put a breakpoint on the query side to see what's hapening.
Reading the related issue
https://issues.apache.org/jira/browse/LUCENE-6212
I see that it aimed at removing
_a trappy API that required deciding at query time which analyzer to use._
> Upgrade text search to latest Lucene
> ------------------------------------
>
> Key: JENA-1250
> URL: https://issues.apache.org/jira/browse/JENA-1250
> Project: Apache Jena
> Issue Type: Improvement
> Components: Jena
> Reporter: Jean-Marc Vanel
>
> We are currently at Lucene 4.9.1 ,
> which is quite outdated compared to latest Lucene, which is 6.2.1 .
> Note that there is project to add a simple completion feature in addition to
> existing simple search.
> But it would be better to do that on an updated Lucene dependency .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
