Yes, the TermsQParser is better than a massive Boolean OR query, which can be limited in number of clauses through config.
Keep in mind that thousands may not work via HTTP GET. Instead, send those queries via HTTP POST and you will be fine. If you are using SolrJ, it has support for routing queries over POST. Regards, Markus 2022-04-21 19:18 GMT+02:00, Matthew Lapointe <[email protected]>: > Hi Neha, > > The terms query parser might be useful for you: > https://solr.apache.org/guide/8_11/other-parsers.html#terms-query-parser. > > It's more concise and gives different options for the underlying query > implementation depending on the use case. > > Matthew > > On Thu, Apr 21, 2022 at 3:14 AM Neha Gupta <[email protected]> wrote: > >> Dear SOLR community, >> >> I have a question related to passing of list of values (for an >> attribute) in SOLR query. >> I want to pass a list of values which can have thousands values in SOLR >> query as i want to have only those records where that attribute value >> lies in that list. >> >> Is there a way to achieve the same or do i need to create a big query >> with OR separated values? like attribute: value1 OR value2 OR value3 and >> so on >> If in case i create a query with the OR separated values will it have >> any affect on the performance? >> >> Requesting your valuable feedback on the same. >> >> >> Regards >> Neha Gupta >> >> >
