You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (Created JIRA)" <ji...@apache.org> on 2012/03/14 09:57:38 UTC
[jira] [Created] (SOLR-3243) eDismax and non-fielded range query
eDismax and non-fielded range query
-----------------------------------
Key: SOLR-3243
URL: https://issues.apache.org/jira/browse/SOLR-3243
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 3.5, 3.4, 3.3, 3.2, 3.1
Reporter: Jan Høydahl
Priority: Critical
Fix For: 3.6, 4.0
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 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
[jira] [Updated] (SOLR-3243) eDismax and non-fielded range query
Posted by "Jan Høydahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl updated SOLR-3243:
------------------------------
Fix Version/s: 5.0
> 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
> Priority: Critical
> Fix For: 5.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
[jira] [Updated] (SOLR-3243) eDismax and non-fielded range query
Posted by "Jan Høydahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl updated SOLR-3243:
------------------------------
Attachment: SOLR-3243.patch
First attempt for patch. This detects a range query without a field, and generates plain literal field queries for the tokens.
> 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
> Priority: Critical
> Fix For: 5.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
[jira] [Updated] (SOLR-3243) eDismax and non-fielded range query
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-3243:
---------------------------
Fix Version/s: (was: 4.0)
removing fixVersion=4.0 since there is no evidence that anyone is currently working on this issue. (this can certainly be revisited if volunteers step forward)
> 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
> Priority: Critical
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
[jira] [Assigned] (SOLR-3243) eDismax and non-fielded range query
Posted by "Jan Høydahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl reassigned SOLR-3243:
---------------------------------
Assignee: Jan Høydahl
> 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
> Priority: Critical
> Fix For: 5.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
[jira] [Commented] (SOLR-3243) eDismax and non-fielded range query
Posted by "Jan Høydahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453021#comment-13453021 ]
Jan Høydahl commented on SOLR-3243:
-----------------------------------
Bill Bell, would you care to test this and comment.
I think there is still a loophole for a bare * query - it gets expanded across all fields as well and is less efficient than a MatchAllDocsQuery, which is more likely to be the intent when issuing a *. Perhaps we can incorporate that in this issue as well?
> 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
> Priority: Critical
> Fix For: 5.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
[jira] [Commented] (SOLR-3243) eDismax and non-fielded range query
Posted by "Bill Bell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232174#comment-13232174 ]
Bill Bell commented on SOLR-3243:
---------------------------------
If production sites are using edismax this seems like a very critical issue.
> 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
> Priority: Critical
> Fix For: 3.6, 4.0
>
>
> 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 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
[jira] [Commented] (SOLR-3243) eDismax and non-fielded range query
Posted by "Bill Bell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232173#comment-13232173 ]
Bill Bell commented on SOLR-3243:
---------------------------------
If production sites are using edismax this seems like a very critical issue.
> 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
> Priority: Critical
> Fix For: 3.6, 4.0
>
>
> 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 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