portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Christopher <j...@animalsinneed.net>
Subject Re: [Proposal] Lucene Search Service
Date Wed, 28 May 2003 18:52:20 GMT
FWIW, when I was tasked to enhance the Category filtetering for our jetspeed 
portal I originally wanted to add a search functionality using Lucene. My 
bosses didn't like the idea because they wanted me to do something that would 
be generic enough to contribute back to the community (i.e. BUg 17839). I 
think Lucene would fit very well into Jetspeed and the results returned could 
very easily fit into what is already displayed when choosing a portlet to 
add. IMO, the updating of the search index could be done by gathering needed 
data from the .xreg files on startup but, should be easily overridden if a 
site chooses to do so.

John Christopher 

On Tuesday 20 May 2003 12:16, Jeremy Ford wrote:
> I've noticed the new LuceneSearchService and have been giving some thought
> as to how I might like to put it to use.  I'll admit to not having that
> much experience with Lucene, so if anyone thinks that this won't work, just
> let me know.
> In terms of the service, perhaps there should be a generic SearchService
> interface of which the Lucene service is an implementation.  That way, if
> there was some other great search engine someone wanted to use, they could
> swap it out.
> I was thinking that there could be 4 basic methods.  These would be
> add(Object o), update(Object o), remove(Object o), and search(query).  In
> order to support more than one object type, we could setup the service to
> accept LuceneDocuement loaders, which would know how to turn the generic
> object into a Lucene document that can be added to the index.  Here's an
> outline.
> services.SearchService.classname=org.apache.jetspeed.services.search.lucene
>.LuceneSearchService services.SearchService.index=WEB-INF/index
> services.SearchService.handler.name=ObjectXHandler
> services.SearchService.handler.ObjectXHandler.classname=com.mycompany.lucen
> services.SearchService.handler.ObjectXHandler.object_type=com.mycompany.Obj
> services.SearchService.handler.name=ObjectYHandler
> services.SearchService.handler.ObjectYHandler.classname=com.mycompany.lucen
> services.SearchService.handler.ObjectYHandler.object_type=com.mycompany.Obj
> So, when it comes time to add the object to the index, the service looks up
> the appropriate object handler, uses it to convert the object to a Lucene
> document, and then adds/updates/removes it from the index.  In terms of
> searching, this would allow all kinds of different indexed documents to be
> returned from a search.  Perhaps a filter could be placed in the search so
> that only certain types of documents that originally came from certain
> types of objects could be returned.
> Again, just an idea.  But it strikes me as a powerful one with respect to a
> general indexing solution.
> Jeremy Ford
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message