On Thu, 11 Oct 2007, Phillip J. Eby wrote:
At 11:58 AM 10/11/2007 -0700, Heikki Toivonen wrote:
In an ideal world Lucene would have been written with Python instead of
Java ;) (I know of the lagging ports, but as long as they lag too much
they don't seem to be an option.)
What are we using Lucene for, exactly? Has CLucene caught up to the features
we use? What do we use that is not available in other tools?
I mean, it doesn't appear we're using custom tokenizers or anything
particularly fancy at the moment.
Currently, we've barely scratched the surface about what we can do with full
text index and search. It was a struggle just to get the search UI into
Preview. You're asking "at the moment" and the answer to that is "not much".
The idea, years ago, was to do a lot more. This is why I expended so much
effort in going the PyLucene route.
Markku had some cool ideas that didn't materialize during his time with us. We
also haven't done anything about making the indexing and searches more
language-aware. Currently all analysis and tokenizations assume US english.
And so on.
If we're not going to do anything more with indexing and search, we sure can
throw Lucene away...
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
