Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 87119 invoked from network); 21 May 2009 16:45:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 May 2009 16:45:18 -0000 Received: (qmail 2699 invoked by uid 500); 21 May 2009 16:45:29 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 2643 invoked by uid 500); 21 May 2009 16:45:29 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 2633 invoked by uid 99); 21 May 2009 16:45:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 16:45:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 16:45:20 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M7BO7-00046L-M9 for solr-user@lucene.apache.org; Thu, 21 May 2009 09:44:59 -0700 Message-ID: <23656522.post@talk.nabble.com> Date: Thu, 21 May 2009 09:44:59 -0700 (PDT) From: Marc Sturlese To: solr-user@lucene.apache.org Subject: Re: Customizing SOLR-236 field collapsing In-Reply-To: <4A157B90.6000503@kabuco.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: marc.sturlese@gmail.com References: <23653220.post@talk.nabble.com> <4A157B90.6000503@kabuco.de> X-Virus-Checked: Checked by ClamAV on apache.org Yes, I have tried it but I see couple of problems doing that. I will have to do more searches so response time will increase. The second thing is that, imagine I show the results collapsed in page one and put a button to see the non collapsed results. If later results for the second page are requested, some results from the non collapsed request would be the same that some results that apeared in the first page doing collapsing: collapsing page 1 shows docs: 1-2-3-6-7 non collapsing results page 1 shows docs: 1-2-3-4-5 collapsing results page 2 shows docs: 8-9-10-11-12 non collapsing results page 2 show docs: 6-7-8-9-10 I want to avoid that and make the response as fast as possible. That is the reason because I want to send the collapsed docs to the end of the queue... Thanks Thomas Traeger-2 wrote: > > Is adding QueryComponent to your SearchComponents an option? When > combined with the CollapseComponent this approach would return the > collapsed and the complete result set. > > i.e.: > > > collapse > query > facet > mlt > highlight > > > Thomas > > Marc Sturlese schrieb: >> Hey there, >> I have been testing the last adjacent field collapsing patch in trunk and >> seems to work perfectly. I am trying to modify the function of it but >> don't >> know exactly how to do it. What I would like to do is instead of collapse >> the results send them to the end of the results cue. >> Aparently it is not possible to do that due to the way it is implemented. >> I >> have noticed that you get a DocSet of the ids that "survived" the >> collapsing >> and that match the query and filters (collapseFilterDocSet = >> collapseFilter.getDocSet();, you get it in CollapseComponent.java. >> Once it is done the search is excuted again, this time the DocSet >> obtained >> before is passed as a filter: >> >> DocListAndSet results = searcher.getDocListAndSet(rb.getQuery(), >> >> collapseFilterDocSet >> == null? rb.getFilters(): null, >> >> collapseFilterDocSet, >> >> rb.getSortSpec().getSort(), >> >> rb.getSortSpec().getOffset(), >> >> rb.getSortSpec().getCount(), >> >> rb.getFieldFlags()); >> >> The result of this search will give you the final result (with the >> correct >> offset and start). >> I have thought in saving the collapsed docs in another DocSet and after >> do >> something with them... but don't know how to manage it. >> Any clue about how could I reach the goal? >> Thanks in advance >> > > > -- View this message in context: http://www.nabble.com/Customizing-SOLR-236-field-collapsing-tp23653220p23656522.html Sent from the Solr - User mailing list archive at Nabble.com.