Unfortunately I do not. It's been on my list, but I've also been concerned about project support. I was heartened to see it listed for the Google Summer of Code, and that write up was about features, rather than stabilization. That said, Lucene is under active development, where as Montezuma is tepid at best.
Another approach is JFLI http://jfli.sourceforge.net/ which gives you Lisp bindings to Java. I *believe* though that it is LispWorks specific, so this may not work. It would be nice to see resurgence in Lisp. Glenn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Eslick Sent: Tuesday, May 13, 2008 11:10 PM To: Elephant bugs and development Subject: Re: [elephant-devel] full text search solution? Thanks Glenn, Do you have experience with Montezuma? Ian On May 13, 2008, at 10:43 PM, Glenn Tarcea wrote: > Never mind, I see from reading that you already found Monezuma.... > But it does look like it might get some activity. > > Glenn > > On May 13, 2008, at 10:33 PM, Glenn Tarcea wrote: > >> Have you looked at Montezuma? http://projects.heavymeta.org/ >> montezuma/ >> >> It's a port of Ferret (which is port of Lucene) to Lisp. It's also >> on the list for the google summer of code to add some additional >> functionality to it. >> >> BTW: If its alright I'm going to update the docs to add a section >> on having two versions of Elephant installed and using ASDF to >> manage them. >> >> Glenn >> >> >> On May 13, 2008, at 10:02 PM, Ian Eslick wrote: >> >>> Hello, >>> >>> Has anyone found a good solution for full text search in lisp? >>> I'm interested in indexing website objects such as posts and >>> perhaps external documents as well. BDB doesn't, to the best of >>> my knowledge, have the appropriate building blocks for an >>> efficient indexing system and you certainly don't want to do it on >>> top of the current btree interface. >>> >>> I have an old full text index code base that supported wildcard >>> and NEAR queries, all built on top of Elephant btrees. It was >>> convenient but had a query time that slowed down linearly with the >>> avg # of documents per word. >>> >>> I've decided that the best approach for me is to connect to a >>> separate, probably external, system to which I can incrementally >>> add content that will return something I can easily turn into an >>> ordered list of OIDs. >>> >>> Most solutions I've run across require other languages, servers >>> that add up to needless complexity for my modest application. In >>> the lisp world I've only seen Montezuma, which isn't being >>> developed or seriously maintained (unless it's just really stable >>> I'd rather not fight with stale code). >>> >>> I am considering hacking something simple on top of postmodern >>> that uses the new text indexing functions of Postgresql 8.3 and >>> wondered if anyone here has insight into this application of >>> postmodern or into the full-text indexing from lisp problem in >>> general. >>> >>> Thank you, >>> Ian >>> _______________________________________________ >>> elephant-devel site list >>> elephant-devel@common-lisp.net >>> http://common-lisp.net/mailman/listinfo/elephant-devel >>> >>> >> >> _______________________________________________ >> elephant-devel site list >> elephant-devel@common-lisp.net >> http://common-lisp.net/mailman/listinfo/elephant-devel > > _______________________________________________ > elephant-devel site list > elephant-devel@common-lisp.net > http://common-lisp.net/mailman/listinfo/elephant-devel _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
