lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-2368) Improve extended dismax (edismax) parser
Date Thu, 02 Feb 2012 01:43:53 GMT

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

Jan Høydahl commented on SOLR-2368:
-----------------------------------

Regarding old DisMax, do all bugs being detected in eDismax also get fixed in DisMax if applicable?
I'm not sure..
If/when eDismax can be configured to fill the original role of DisMax, why should we maintain
the old one?
And if edismax was the one written first, it would have the name "dismax", so why could it
not get that name the day it supersedes dismax in features and usage?

It's a bit analogue to IntField/TrieIntField - naming hints on implementation details to distinguish
from other implementations, but if TrieIntField was developed in one go and not committed
incrementally, it could simply have replaced IntField. eDisMax is @lucene.experimental and
when it is up to par with dismax all over, it should in my opinion take over its name with
a fat notice in CHANGES.TXT. For a few versions edismax could be a valid alias too, and the
old dismax could be kept around as "legacydismax" for the conservative/lazy. How would you
like to have to relate to EnhancedCsvUpdateRequestHandler at /solr/update/ecsv just because
the original is less complex? :-)

Created SOLR-3086 to let users lobotomize edismax so it will only accept the query syntaxes
they choose.

                
> Improve extended dismax (edismax) parser
> ----------------------------------------
>
>                 Key: SOLR-2368
>                 URL: https://issues.apache.org/jira/browse/SOLR-2368
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>            Reporter: Yonik Seeley
>              Labels: QueryParser
>
> This is a "mother" issue to track further improvements for eDismax parser.
> The goal is to be able to deprecate and remove the old dismax once edismax satisfies
all usecases of dismax.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


Mime
View raw message