Hi Joel, Thank you for the reply. I created https://issues.apache.org/jira/browse/SOLR-5773 for this new feature. I was looking at the getBoostDocs() function and if I understand it correctly it iterates through the boosted set that is passed into the function and then iterates over the boosted Set<String> and casts each element to a BytesRef and stores it in a HashSet. While I'm confused what all the type conversion is actually doing I can follow the logic somewhat. You then traverse the index and retrieve all of the terms for the uniqueid of the schema. You then seek in the localBoosts hashset for the current document and if it is in the index you add it to boostDocs to be returned from the function as well as remove the document from the localBoosts hashset. I don't think the document is actually removed from the result set in this function however. I spent some hours today trying to decipher some of this code. I am very interested in understanding this code so that I can contribute back to this project but I am finding it all a bit daunting. As always your help is greatly appreciated and thank you for the quick response.
On Tue, Feb 25, 2014 at 5:38 PM, Joel Bernstein [via Lucene] < ml-node+s472066n411966...@n3.nabble.com> wrote: > Hi David, > > Just read through your comments on the jira. Feel free to create a jira > for > this. The way this currently works is that if the elevated document is not > the selected group head, then both the elevated document and the group > head > are in the result set. What you are suggesting is that the elevated > document becomes the group head. We can discuss the best way to handle > this > on the new ticket. > > Joel > > Joel Bernstein > Search Engineer at Heliosearch > > > On Tue, Feb 25, 2014 at 1:29 PM, dboychuck <[hidden > email]<http://user/SendEmail.jtp?type=node&node=4119662&i=0>> > wrote: > > > https://issues.apache.org/jira/browse/SOLR-5773 > > > > I am having trouble with CollapseQParserPlugin showing duplicate groups > > when > > the search results contain a member of a grouped document but another > > member > > of that grouped document is defined in the elevate component. I have > > described the issue in more detail here: > > https://issues.apache.org/jira/browse/SOLR-5773 > > > > Any help is appreciated. Also any hints as to how I can solve this > problem > > myself would be great as I'm having a bit of trouble understanding the > code > > to implement a fix. > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596p4119662.html > To unsubscribe from CollapseQParserPlugin problem with ElevateComponent, > click > here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4119596&code=ZGJveWNodWNrQGJ1aWxkLmNvbXw0MTE5NTk2fDE3MjM1MzAyMTk=> > . > NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- *David Boychuck* Software Engineer Search, Team Lead Build.com, Inc. <http://corp.build.com/> Smarter Home Improvement(tm) P.O. Box 7990 Chico, CA 95927 *P*: 800.375.3403 *F*: 530.566.1893 dboych...@build.com | Network of Stores<http://www.build.com/index.cfm?page=help:networkstores&source=emailSignature> -- View this message in context: http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596p4119680.html Sent from the Solr - User mailing list archive at Nabble.com.
