[
https://issues.apache.org/jira/browse/SOLR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198773#comment-13198773
]
Jan Høydahl commented on SOLR-2368:
-----------------------------------
Personally I don't think we should worry about the added features after edismax
becomes dismax. If people don't read the release notes when upgrading, they
cannot complain later: "Noone told me that fuzzy queries was allowed by
dismax". Especially if we provide a way to turn it off. In worst case I can
commit to changing the config defaults for edismax to resemble dismax
behaviour, i.e. uf=-*&us.all=false (see SOLR-3086).
Anyone of you out there using "dismax" over "edismax" for other reasons than
the ones already mentioned?
> 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: [email protected]
For additional commands, e-mail: [email protected]
