If there's enough interest, I might get back into the code and throw a
standalone src (and jar) of the SpanQueryParser and the Solr wrapper onto
github. That would make it more widely available until there's a chance to
integrate it into Lucene/Solr. If you'd be interested in this, let me know
(and/or vote on the issue pages on Jira).
Best,
Tim
-----Original Message-----
From: Michael Ryan [mailto:mr...@moreover.com]
Sent: Tuesday, July 01, 2014 9:24 AM
To: solr-user@lucene.apache.org
Subject: RE: Multiterm analysis in complexphrase query
Thanks. This looks interesting...
-Michael
-----Original Message-----
From: Allison, Timothy B. [mailto:talli...@mitre.org]
Sent: Monday, June 30, 2014 8:15 AM
To: solr-user@lucene.apache.org
Subject: RE: Multiterm analysis in complexphrase query
Ahmet, please correct me if I'm wrong, but the ComplexPhraseQueryParser does
not perform analysis (as you, Michael, point out). The SpanQueryParser in
LUCENE-5205 does perform analysis and might meet your needs. Work on it has
gone on pause, though, so you'll have to build from the patch or the
LUCENE-5205 branch. Let me know if you have any questions.
LUCENE-5470 and LUCENE-5504 would move multiterm analysis farther down and make
it available to all parsers that use QueryParserBase, including the
ComplexPhraseQueryParser.
Best,
Tim
-----Original Message-----
From: Michael Ryan [mailto:mr...@moreover.com]
Sent: Sunday, June 29, 2014 11:09 AM
To: solr-user@lucene.apache.org
Subject: Multiterm analysis in complexphrase query
I've been using a modified version of the complex phrase query parser patch
from https://issues.apache.org/jira/browse/SOLR-1604 in Solr 3.6, and I'm
currently upgrading to 4.9, which has this built-in.
I'm having trouble with using accents in wildcard queries, support for which
was added in https://issues.apache.org/jira/browse/SOLR-2438. In 3.6, I was
using a modified version of SolrQueryParser, which simply used
ComplexPhraseQueryParser in place of QueryParser. In the version of
ComplexPhraseQParserPlugin in 4.9, it just directly uses
ComplexPhraseQueryParser, and doesn't go through SolrQueryParser at all.
SolrQueryParserBase.analyzeIfMultitermTermText() is where the multiterm
analysis magic happens.
So, my problem is that ComplexPhraseQParserPlugin/ComplexPhraseQueryParser
doesn't use SolrQueryParserBase, which breaks doing fun things like this:
{!complexPhrase}"barac* óba*a"
And expecting it to match "Barack Obama".
Anyone run into this before, or have a way to get this working?
-Michael
