[
https://issues.apache.org/jira/browse/PYLUCENE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029674#comment-13029674
]
Christopher Currens commented on PYLUCENE-9:
--------------------------------------------
I was very hesitant to report this as a bug, since pylucene isn't a port,
rather just recompiled. I am positive I am comparing the correct versions (I'm
a committer on Lucene.Net). I'll show you all the configurations I've done:
Lucene.Net 2.9.2 - Valid
Lucene.Net 2.9.4 - Valid
Java Lucene (via Luke 1.0.1 (uses Lucene 2.9.4)) - Valid
Java Lucene (via Luke 3.1.0 (uses > Lucene 3.0)) - Valid
pyLucene (Lucene 2.9.2) - Invalid replaced by single Wildcard ('?')
pyLucene (Lucene 2.9.4) - Invalid replaced by single Wildcard ('?')
pyLucene (Lucene 3.0.3) - Invalid replaced by single Wildcard ('?')
Those tests are all on the 32-bin Win-XP. The ubuntu box I've used was using
pyLucene w/ lucene 2.9.2.
One thing I hadn't considered, though, was to see if it can be replicated
outside of the many machines I've used myself to test, specifically if there's
in issue with our building of it via JCC, or something in our environment. But
considering I've tried it at work and at home, there's no real other place I
can test it.
> 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
> <Query: FullText:"calendar item ? msg">
> >>> analyzer = StopAnalyzer(Version.LUCENE_30)
> >>> query = QueryParser(Version.LUCENE_30)
> >>> parsedQuery = query.parse("\"Calendar Item as Msg\"")
> >>> parsedQuery
> <Query: FullText:"calendar item ? msg">
> 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
