romseygeek commented on PR #14759: URL: https://github.com/apache/lucene/pull/14759#issuecomment-2955166917
Well it's still an optimization, but just at the cost of a bigger query footprint. I think there are a couple of things pulling in different directions here: * IndexOrDocValuesQuery trades off in-memory complexity for better query-time performance * We have the too many clauses check to push people towards using queries that use less memory, eg TermInSetQuery instead of very large disjunctions of TermQuery So what you're running into there is the limit of that trade-off. I don't think anything is wrong here, I think this is telling us that if you want to do a disjunction over ranges then past a certain point just building a boolean query is going to be very inefficient and you should use a different type of query. Maybe one that we don't actually provide yet! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
