Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 18 Feb 2011 00:53:12 +0000 (UTC)
From: "Hoss Man (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1328621616.596.1297990392030.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <461567828.280.1297876104366.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (SOLR-2368) Improve extended dismax (edismax)
 parser
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996181#comment-12996181 ] 

Hoss Man commented on SOLR-2368:
--------------------------------

bq. for example fielded queries work by default. It's the type of change in defaults we'd want to make anyway,

on that point alone i'd pretty much completley disagree with you -- the spirt of dismax is locking odwn what users can access via the "q" param by putting those controls in other params.  i don't want some users who inadvertantly/maliciously guesses one of hte field names in my schema to suddenly have differnet query behavior unless i explicitly enable that feature.

> Improve extended dismax (edismax) parser
> ----------------------------------------
>
>                 Key: SOLR-2368
>                 URL: https://issues.apache.org/jira/browse/SOLR-2368
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Yonik Seeley
>
> Improve edismax and replace dismax once it has all of the needed features.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org