On May 16, 2006, at 12:51 PM, Marvin Humphrey wrote:
> How many users here care about Lucene compatibility, and why?
Personally I'm putting my eggs into the Solr basket - http://
incubator.apache.org/solr
Solr has a ton of benefits over using raw Lucene with its caching and
configurable handling of putting new searchers online, etc. Its got
plenty of room for improvement, and those improvements are in
progress. I am integrating Solr into a Ruby on Rails front-end as we
speak, but doing so crudely through a rough HTTP API, but abstracting
that communication layer behind a nice Rubyish DSL would be quite cool.
I used to really really want Lucene index compatibility at the file
format layer along with a really fast Ruby implementation. At this
point I've changed my mind and Solr is my recommended basis for
search integration into non-Java (and even Java perhaps) applications.
I just wanted to toss out my thoughts since I've been mostly silent
on the Ferret/KinoSearch issues. I still day dream of GCJ'd Java
Lucene being the basis for cross-language integration using PyLucene
as a great example. They achieve 100% index compatibility with Java
Lucene because it *is* Java Lucene. I'm still extremely pleased to
see folks like Dave and Marvin digging deep in to Ruby and Perl
integration and starting to work together. Very promising no matter
how this ends up. I'm optimistic we'll have Lucene in Ruby one of
these days in a compatible way and incredibly performant way!
Erik
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
