[
https://issues.apache.org/jira/browse/PYLUCENE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031284#comment-13031284
]
Christopher Currens commented on PYLUCENE-9:
Hmm, the code I have is nearly identical, and when I pull it out of the
contained code, it behaves as it should. I can't post the whole code, but the
issue must be that there's a lingering Version.LUCENE_24 somewhere I suppose.
I'll try figuring it out on my own, I'm glad to see its something idiotic I've
done. :)
> QueryParser replacing stop words with wildcards
> ---
>
> Key: PYLUCENE-9
> URL: https://issues.apache.org/jira/browse/PYLUCENE-9
> Project: PyLucene
> Issue Type: Bug
> Environment: Windows XP 32-bit Sp3, Ubuntu 10.04.2 LTS i686
> GNU/Linux, jdk1.6.0_23
>Reporter: Christopher Currens
>
> Was using query parser to build a query. In Java Lucene (as well as
> Lucene.Net), the query "Calendar Item as Msg" (quotes included), is parsed
> properly as FullText:"calendar item msg" in Java Lucene and Lucene.Net. In
> pylucene, it is parsed as: FullText:"calendar item ? msg". This causes
> obvious problems when comparing search results from python, java and .net.
> Initially, I thought it was the Analyzer I was using, but I've tried the
> StandardAnalyzer and StopAnalyzer, which work properly in Java and .Net, but
> not pylucene.
> Here is code I've used to reproduce the issue:
> >>> from lucene import StandardAnalyzer, StopAnalyzer, QueryParser, Version
> >>> analyzer = StandardAnalyzer(Version.LUCENE_30)
> >>> query = QueryParser(Version.LUCENE_30, "FullText", analyzer)
> >>> parsedQuery = query.parse("\"Calendar Item as Msg\"")
> >>> parsedQuery
>
> >>> analyzer = StopAnalyzer(Version.LUCENE_30)
> >>> query = QueryParser(Version.LUCENE_30)
> >>> parsedQuery = query.parse("\"Calendar Item as Msg\"")
> >>> parsedQuery
>
> I've noticed this in pylucene 2.9.4, 2.9.3, and 3.0.3
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
