You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2016/10/22 03:42:58 UTC
[jira] [Commented] (SOLR-2216) Highlighter query exceeds
maxBooleanClause limit due to range query
[ https://issues.apache.org/jira/browse/SOLR-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15597068#comment-15597068 ]
Cao Manh Dat commented on SOLR-2216:
------------------------------------
Currently, I do not think this is a problem of Solr. Because the code to create QueryScorer for Highlighting is quite simple
{code}
QueryScorer scorer = new QueryScorer(query,
hl.requireFieldMatch == true ? fieldName : null);
{code}
and
{code}
if (reqFieldMatch) {
return new QueryTermScorer(query, request.getSearcher().getIndexReader(), fieldName);
} else {
return new QueryTermScorer(query);
}
{code}
I think it is related to how Lucene rewrite the query, will try to dig deeper into Lucene code and figure out the changes.
> Highlighter query exceeds maxBooleanClause limit due to range query
> -------------------------------------------------------------------
>
> Key: SOLR-2216
> URL: https://issues.apache.org/jira/browse/SOLR-2216
> Project: Solr
> Issue Type: Bug
> Components: highlighter
> Affects Versions: 1.4.1
> Environment: Linux solr-2.bizjournals.int 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
> JAVA_OPTS="-client -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=8888 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.access.file=/root/.jmxaccess -Dcom.sun.management.jmxremote.password.file=/root/.jmxpasswd -Dcom.sun.management.jmxremote.ssl=false -XX:+UseCompressedOops -XX:MaxPermSize=512M -Xms10240M -Xmx15360M -XX:+UseParallelGC -XX:+AggressiveOpts -XX:NewRatio=5"
> top - 11:38:49 up 124 days, 22:37, 1 user, load average: 5.20, 4.35, 3.90
> Tasks: 220 total, 1 running, 219 sleeping, 0 stopped, 0 zombie
> Cpu(s): 47.5%us, 2.9%sy, 0.0%ni, 49.5%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 24679008k total, 18179980k used, 6499028k free, 125424k buffers
> Swap: 26738680k total, 29276k used, 26709404k free, 8187444k cached
> Reporter: Ken Stanley
>
> For a full detail of the issue, please see the mailing list: http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201011.mbox/%3CAANLkTimE8z8yOni+u0Nsbgct1=eF7E+sU0_WAKu2cMno@mail.gmail.com%3E
> The nutshell version of the issue is that when I have a query that contains ranges on a specific (non-highlighted) field, the highlighter component is attempting to create a query that exceeds the value of maxBooleanClauses set from solrconfig.xml. This is despite my explicit setting of hl.field, hl.requireFieldMatch, and various other hightlight options in the query.
> As suggested by Koji in the follow-up response, I removed the range queries from my main query, and SOLR and highlighting were happy to fulfill my request. It was suggested that if removing the range queries worked that this might potentially be a bug, hence my filing this JIRA ticket. For what it is worth, if I move my range queries into an fq, I do not get the exception about exceeding maxBooleanClauses, and I get the effect that I was looking for.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org