Re: switch query parser and solr cloud

2018-09-13 Thread Dwane Hall
"start":0, "allResults":"false", "fl":"FIELD_1,FIELD_2,SUMMARY_FIELD", "fq":"{!switch default=\"{!collapse field=SUMMARY_FIELD}\" case.true=*:* v=${allResults}}", Somewhat odd. Thanks again t

Re: switch query parser and solr cloud

2018-09-12 Thread Dwane Hall
sing this issue. Thanks again for both of your input Cheers, Dwane From: Erick Erickson Sent: Thursday, 13 September 2018 12:20 AM To: solr-user Subject: Re: switch query parser and solr cloud You will run into significant problems if, when returning "all

Re: switch query parser and solr cloud

2018-09-12 Thread Erick Erickson
You will run into significant problems if, when returning "all results", you return large result sets. For regular queries I like to limit the return to 100, although 1,000 is sometimes OK. Millions will blow you out of the water, use CursorMark or Streaming for very large result sets. CursorMark

Re: switch query parser and solr cloud

2018-09-12 Thread Shawn Heisey
On 9/12/2018 5:47 AM, Dwane Hall wrote: Good afternoon Solr brains trust I'm seeking some community advice if somebody can spare a minute from their busy schedules. I'm attempting to use the switch query parser to influence client search behaviour based on a client specified request parameter.

switch query parser and solr cloud

2018-09-12 Thread Dwane Hall
Good afternoon Solr brains trust I'm seeking some community advice if somebody can spare a minute from their busy schedules. I'm attempting to use the switch query parser to influence client search behaviour based on a client specified request parameter. Essentially I want the following to occu