Hello, The problem seem to have been solved (still some testing is required). But I stumbled upon another issue.. which requires telling a bit about the use case.
I would like to "by-pass" the maxBooleanClauses limit in such a way, that those queries that contain boolean clauses more than maxBooleanClauses in the number, would be automatically split into sub-queries. That part is done. Now, when such a query arrives, solr throws org.apache.lucene.queryParser.ParseException: Cannot parse 'AccessionNumber:(TS-E_284668 OR TS-E_284904 OR 0000950123-11-086962 OR TS-AS_292840 OR TS-AS_295661 OR TS-AS_296320 OR TS-AS_296805 OR TS-AS_296819 OR TS-AS_296820)': too many boolean clauses one way to avoid this is to set maxBooleanClauses to some large number and maintain a real maxBooleanClauses value inside the code. But is there a better way to handle this? Thanks. On Thu, Jan 12, 2012 at 4:49 PM, Dmitry Kan <dmitry....@gmail.com> wrote: > Hello list, > > I need to split the incoming original facet query into a list of > sub-queries. The logic is done and each sub-query gets added into outgoing > queue with rb.addRequest(), where rb is instance of ResponseBuilder. > In the logs I see that along with the sub-queries the original query gets > submitted too. Is there a way of suppressing the original query? > > -- > Regards, > > Dmitry Kan > -- Regards, Dmitry Kan
