[
https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-3243:
------------------------------------
Priority: Major (was: Critical)
Bumping priority down from Critical since it's clearly not 5+ years into its
life.
I also duplicated the issue (without trying the earlier patch) and noticed that
the query is expanded only to the default search fields (df fields) for the
request handler. I point this out only to note that users with lots of fields
defined for df would have a worse time with this behavior than users who don't
have a lot of fields defined.
> eDismax and non-fielded range query
> -----------------------------------
>
> Key: SOLR-3243
> URL: https://issues.apache.org/jira/browse/SOLR-3243
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 3.1, 3.2, 3.3, 3.4, 3.5
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-3243.patch
>
>
> Reported by Bill Bell in SOLR-3085:
> If you enter a non-fielded open-ended range in the search box, like [* TO *],
> eDismax will expand it to all fields:
> {noformat}
> +DisjunctionMaxQuery((content:[* TO *]^2.0 | id:[* TO *]^50.0 | author:[* TO
> *]^15.0 | meta:[* TO *]^10.0 | name:[* TO *]^20.0))
> {noformat}
> This does not make sense, and a side effect is that range queries for strings
> are very expensive, open-ended even more, and you can totally crash the
> search server by hammering something like ([* TO *] OR [* TO *] OR [* TO *])
> a few times...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
