Project

General

Profile

Bug #8731

Indexing solr client method is building query with too many ORs, causing errors

Added by Rob Nahf about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_indexer
Target version:
Start date:
2018-10-04
Due date:
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

davev [2:17 PM]
@rob - for that massive solr query with 1500 OR terms, not sure if this approach is more efficient, but might be worth investigating: https://harmssite.com/2012/09/solr-query-for-mimicking-sql-in-operator-functionality/
harmssite.com
Solr Query for Mimicking SQL IN Operator Functionality
A Web Development Blog
davev [2:25 PM]
ah, except we have defaultOperator as "AND"
which I just verified can be overridden by adding &q.op=OR to the request
davev [2:43 PM]
I think it was id:* AND resourceMap:(("some id") OR ("another id") OR .... ))
I just verified that using the abbreviated form of q.op=OR&q=resourceMap:("some id" "another id" ...) still causes the same error of too many boolean clauses
so though more efficient in terms of size, it won't solve the issue
ah, but there is a setting in solrconfig.xml, <maxBooleanClauses>1024</maxBooleanClauses>

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)