Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of brad.giaccio@gmail.com
 designates 209.85.132.246 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=lUtYFMhcrLUqL2Gma4dt9RYXO0BSheGIOUomekBSyKtpPVkkpbIv/Vx6h80mJaE73F
         8OgYhpbycieSlpS/v6kT/vhWa7MQIKetyIVFti7bQKlF5fl5QzspG+5HBdiB55aFfaWP
         qxkiECUAfBKMP045PtKPg4nt+GHNRREFyP5Qk=
MIME-Version: 1.0
In-Reply-To: <78643995.1246990574890.JavaMail.jira@brutus>
References: <1740299645.1221101924312.JavaMail.jira@brutus>
	<78643995.1246990574890.JavaMail.jira@brutus>
From: Brad Giaccio <brad.giaccio@gmail.com>
Date: Tue, 7 Jul 2009 14:19:25 -0400
Message-ID: <9362e4bb0907071119y6b387384lc5f873fc89b90986@mail.gmail.com>
Subject: Re: [jira] Commented: (SOLR-769) Support Document and Search Result
	clustering
To: solr-dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=0016e644cc6eca668b046e21aa12

--0016e644cc6eca668b046e21aa12
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

No problem, but now that you are the assignee perhaps you can apply it for
me, its attached to the ticket as 'clustering-component-shard.patch'  and it
includes update junit tests.

If it needs some work now that you have made some output changes I'll be
glad to update.

Thanks,
Brad

On Tue, Jul 7, 2009 at 2:16 PM, Yonik Seeley (JIRA) <jira@apache.org> wrote:

>
>    [
> https://issues.apache.org/jira/browse/SOLR-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728271#action_12728271]
>
> Yonik Seeley commented on SOLR-769:
> -----------------------------------
>
> Apologies Brad - I didn't realize there were pending patches or I would
> have not done the reformat.
>
> > Support Document and Search Result clustering
> > ---------------------------------------------
> >
> >                 Key: SOLR-769
> >                 URL: https://issues.apache.org/jira/browse/SOLR-769
> >             Project: Solr
> >          Issue Type: New Feature
> >            Reporter: Grant Ingersoll
> >            Assignee: Yonik Seeley
> >            Priority: Minor
> >             Fix For: 1.4
> >
> >         Attachments: clustering-componet-shard.patch,
> clustering-libs.tar, clustering-libs.tar, SOLR-769-analyzerClass.patch,
> SOLR-769-lib.zip, SOLR-769.patch, SOLR-769.patch, SOLR-769.patch,
> SOLR-769.patch, SOLR-769.patch, SOLR-769.patch, SOLR-769.patch,
> SOLR-769.patch, SOLR-769.patch, SOLR-769.patch, SOLR-769.patch,
> SOLR-769.patch, SOLR-769.patch, SOLR-769.tar, SOLR-769.zip
> >
> >
> > Clustering is a useful tool for working with documents and search
> results, similar to the notion of dynamic faceting.  Carrot2 (
> http://project.carrot2.org/) is a nice, BSD-licensed, library for doing
> search results clustering.  Mahout (http://lucene.apache.org/mahout) is
> well suited for whole-corpus clustering.
> > The patch I lays out a contrib module that starts off w/ an integration
> of a SearchComponent for doing clustering and an implementation using
> Carrot.  In search results mode, it will use the DocList as the input for
> the cluster.   While Carrot2 comes w/ a Solr input component, it is not the
> same as the SearchComponent that I have in that the Carrot example actually
> submits a query to Solr, whereas my SearchComponent is just chained into the
> Component list and uses the ResponseBuilder to add in the cluster results.
> > While not fully fleshed out yet, the collection based mode will take in a
> list of ids or just use the whole collection and will produce clusters.
>  Since this is a longer, typically offline task, there will need to be some
> type of storage mechanism (and replication??????) for the clusters.  I _may_
> push this off to a separate JIRA issue, but I at least want to present the
> use case as part of the design of this component/contrib.  It may even make
> sense that we split this out, such that the building piece is something like
> an UpdateProcessor and then the SearchComponent just acts as a lookup
> mechanism.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

--0016e644cc6eca668b046e21aa12--