I absolutely agree with your first point. For second point, I agree for defType (so that it affects 'q') but not all the other numerous spots. As far as pushing down into Lucene; if you haven't noticed, Solr now has its own copy of the Lucene's query parser so it can customize it. This is a good thing that was inevitable IMO. ~ David ________________________________ From: Jack Krupansky-2 [via Lucene] [ml-node+s472066n4022841...@n3.nabble.com] Sent: Wednesday, November 28, 2012 1:07 AM To: Smiley, David W. Subject: Re: dismax vs edismax
My view is that if we simply added an option to edismax to restrict the syntax to the very limited syntax of dismax, then we could have one, common xdismax query parser. And then, why not simply rename the current Solr query parser to "classic" and make the new xdismax be the default Solr query parser. And then... push a lot of the so-called "Solr-specific" features down into the Lucene query parser (abstracting away the specifics of Solr schema, Solr plugin, Solr parameter format, etc.) and then we can have one, unified query parser for Lucene and Solr. But... not everyone is persuaded! -- Jack Krupansky -----Original Message----- From: David Smiley (@MITRE.org) Sent: Tuesday, November 27, 2012 11:43 PM To: [hidden email]<UrlBlockedError.aspx> Subject: dismax vs edismax It was my hope that by now, the dismax & edismax distinction would be a thing of the past, such that we'd simply call this by one name, simply "dismax". >From memories of various JIRA commentary, Jan wants this too and made great progress enhancing edismax, but Hoss pushed back on edismax overtaking dismax as "the" one new dismax. I see this as very unfortunate, as having both complicates things and makes it harder to write them in books ;-) I'd love to simply say "dismax" without having to say "edismax" or wonder if when someone said "dismax" they meant "edismax", etc. Does anyone see this changing / progressing? ~ David ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/dismax-vs-edismax-tp4022834.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email]<UrlBlockedError.aspx> For additional commands, e-mail: [hidden email]<UrlBlockedError.aspx> --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email]<UrlBlockedError.aspx> For additional commands, e-mail: [hidden email]<UrlBlockedError.aspx> ________________________________ If you reply to this email, your message will be added to the discussion below: http://lucene.472066.n3.nabble.com/dismax-vs-edismax-tp4022834p4022841.html To unsubscribe from dismax vs edismax, click here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4022834&code=RFNNSUxFWUBtaXRyZS5vcmd8NDAyMjgzNHwxMDE2NDI2OTUw>. NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/dismax-vs-edismax-tp4022834p4022957.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com.
