lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2216) Highlighter query exceeds maxBooleanClause limit due to range query
Date Mon, 24 Oct 2016 15:56:58 GMT

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

Cassandra Targett commented on SOLR-2216:
-----------------------------------------

[~caomanhdat], I added a link from this issue to LUCENE-7520 since I noticed this issue mentioned
in the description there. Now that that issue is committed, do you believe we can close this?
Or is there another test you'd like to run first?

> 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


Mime
View raw message