in reply to Why? - Writing inverted index code in perl might be overkill
in thread Writing a Search Engine in Perl?
I have some expiriences with WAIT (and some pending patches at http://svn.rot13.org/~dpavlin/svnweb/index.cgi/wait/log/trunk/ ), swish-e, Xapian (another great engine which updated perl bindings few days ago). I also experimented with CLucene perl bindings and finally ended with HyperEstraier.
I would suggent to make list of requirements of search engine and then select right one. My current list include:
- full text search
- filter results by attributes (e.g. date, category...)
- ability to update index content while running searches on it
- wildcard support (or substring, even better!)
- acceptable speed on projected amount of data
Writing good parsers and analyzers for input formats (do you want to rank bold words more than surround text?) and font-end is hard enough without writing own reverse index implementation, especially since some very good allready exist.
2share!2flame...
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Why? - Writing inverted index code in perl might be overkill
by Anonymous Monk on Apr 09, 2007 at 16:28 UTC |