Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 58981 invoked from network); 13 Nov 2009 00:03:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Nov 2009 00:03:02 -0000 Received: (qmail 6272 invoked by uid 500); 13 Nov 2009 00:03:02 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 6199 invoked by uid 500); 13 Nov 2009 00:03:02 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 6187 invoked by uid 99); 13 Nov 2009 00:03:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Nov 2009 00:03:01 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Nov 2009 00:02:59 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 95F8C234C1EF for ; Thu, 12 Nov 2009 16:02:39 -0800 (PST) Message-ID: <1013700525.1258070559612.JavaMail.jira@brutus> Date: Fri, 13 Nov 2009 00:02:39 +0000 (UTC) From: "Hoss Man (JIRA)" To: solr-dev@lucene.apache.org Subject: [jira] Commented: (SOLR-1553) extended dismax query parser In-Reply-To: <180617789.1257893127966.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777289#action_12777289 ] Hoss Man commented on SOLR-1553: -------------------------------- I haven't looked at the patch, and i hope to find some time to do so prior to year with a "3" in it, but in the meantime... bq. I guess one of the main questions is if this should remain separate from dismax, or if it should eventually replace dismax? I think the right way to handle this is to let both *classes* coexist in the code base, but to start encouraging people to use the new/improved version by changing the default used when defType=dismax ... a note in CHANGES.txt that people who really want the old class should use defType=oldDismax, or explicitly declare the old parsing using the name "dismax" seems totally suitable (much as we did with LegacyDateField, and lucenePlusSort. bq. Having the capability to do field selections from the query string can often be undesirable, if not even a security issue in some cases. Assuming the new parser is well written (and i would expect nothing less from all you lucid folks) i imagine it wouldn't take too much work to make all of those various options controllable by params. if nothing else, an "escapeTheseChars" type option would be nice brute force way to disable some stuff. > extended dismax query parser > ---------------------------- > > Key: SOLR-1553 > URL: https://issues.apache.org/jira/browse/SOLR-1553 > Project: Solr > Issue Type: New Feature > Reporter: Yonik Seeley > Fix For: 1.5 > > Attachments: SOLR-1553.patch > > > An improved user-facing query parser based on dismax -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.