I don't recall hearing any discussion of such a switch. In fact, Solr now
has its own copy of the classic Lucene query parser since Solr needed some
features that the Lucene guys did not find acceptable.
That said, if you have a proposal to dramatically upgrade the base Solr
query parser, as well as edismax, I'm sure people would be interested. I
think the intent was to evolve edismax to the point where it would become
the default Solr query parser.
So, maybe that would be the ideal starting point - a version of edismax
based on the flexible query parser rather than the classic query parser.
-- Jack Krupansky
-----Original Message-----
From: Karsten R.
Sent: Tuesday, December 03, 2013 1:24 AM
To: solr-user@lucene.apache.org
Subject: Using the flexible query parser in Solr instead of classic
Hi folks,
last year we built a 3.X Solr-QueryParser based on
org.apache.lucene.queryparser.flexible.standard.StandardQueryParser because
we had some additions with SpanQueries and PhraseQueries. We think about to
adapt this for 4.X
At time the SolrQueryParser is based on
org.apache.lucene.queryparser.classic.QueryParser.jj
Is there a plan for 4.X to switch with LuceneQParser from classic to
flexible (
org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.jj
)?
Is there a SOLR-Task to use the flexible QP ?
Is this a need for someone else?
Beste regards
Karsten
P.S. I did only found one (unanswered) Thread and no Task about Solr and
flexible QP (Thread:
http://lucene.472066.n3.nabble.com/Using-the-contrib-flexible-query-parser-in-Solr-td3333819.html
)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Using-the-flexible-query-parser-in-Solr-instead-of-classic-tp4104584.html
Sent from the Solr - User mailing list archive at Nabble.com.
