Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3DF6E3A2 for ; Wed, 28 Nov 2012 05:25:02 +0000 (UTC) Received: (qmail 24128 invoked by uid 500); 28 Nov 2012 05:25:01 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 23948 invoked by uid 500); 28 Nov 2012 05:25:00 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 23890 invoked by uid 99); 28 Nov 2012 05:24:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 05:24:58 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of SRS0=2VkTHF=JY=basetechnology.com=jack@yourhostingaccount.com designates 65.254.253.28 as permitted sender) Received: from [65.254.253.28] (HELO mailout03.yourhostingaccount.com) (65.254.253.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 05:24:51 +0000 Received: from mailscan07.yourhostingaccount.com ([10.1.15.7] helo=mailscan07.yourhostingaccount.com) by mailout03.yourhostingaccount.com with esmtp (Exim) id 1Tda8M-0000dr-5C for dev@lucene.apache.org; Wed, 28 Nov 2012 00:24:30 -0500 Received: from impout01.yourhostingaccount.com ([10.1.55.1] helo=impout01.yourhostingaccount.com) by mailscan07.yourhostingaccount.com with esmtp (Exim) id 1Tda8M-00072l-03 for dev@lucene.apache.org; Wed, 28 Nov 2012 00:24:30 -0500 Received: from authsmtp14.yourhostingaccount.com ([10.1.18.14]) by impout01.yourhostingaccount.com with NO UCE id UtQV1k0050JCsUy01tQVub; Wed, 28 Nov 2012 00:24:29 -0500 X-Authority-Analysis: v=2.0 cv=EJGEIilC c=1 sm=1 a=yH02RjTyxywMAIqhn74x1Q==:17 a=aQzbgH187woA:10 a=3jZET7lWBKwA:10 a=8nJEP1OIZ-IA:10 a=jvYhGVW7AAAA:8 a=iWDZHbV_kiYA:10 a=sMBj6sIwAAAA:8 a=mV9VRH-2AAAA:8 a=rFdad-MWAAAA:8 a=9I5xiGouAAAA:8 a=NJJsfQfok34OyjB3tMIA:9 a=wPNLvfGTeEIA:10 a=cMDNpJNjNW4A:10 a=2fPOlPt4dusA:10 a=3iK1i4ecmUoA:10 a=rcbtdQGuPFtN9R+ZKREELQ==:117 X-EN-OrigOutIP: 10.1.18.14 X-EN-IMPSID: UtQV1k0050JCsUy01tQVub Received: from 207-237-113-14.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com ([207.237.113.14] helo=JackKrupansky) by authsmtp14.yourhostingaccount.com with esmtpa (Exim) id 1Tda8L-0002IB-Lx for dev@lucene.apache.org; Wed, 28 Nov 2012 00:24:29 -0500 Message-ID: <96B50AAA6A3C4E76A77CF7A877171C88@JackKrupansky> From: "Jack Krupansky" To: References: <1354077819942-4022834.post@n3.nabble.com> In-Reply-To: <1354077819942-4022834.post@n3.nabble.com> Subject: Re: dismax vs edismax Date: Wed, 28 Nov 2012 00:24:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-EN-UserInfo: e0a4b55451ed9f27313ebf02e3d4348d:fc4a93e1349e680c52bdd723c0ab3ef6 X-EN-AuthUser: jack@basetechnology.com Sender: "Jack Krupansky" X-EN-OrigIP: 207.237.113.14 X-EN-OrigHost: 207-237-113-14.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com X-Virus-Checked: Checked by ClamAV on apache.org 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: dev@lucene.apache.org 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: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org