460998d512
This provides a much cleaner separation of concerns, and makes it possible to get rid of a lot of the gunkier parts of the index service. It will also permit lowering the Xmx on the index service a fair bit, so we can get CompressedOOps again :D |
||
|---|---|---|
| .. | ||
| domain-ranking | ||
| index-forward | ||
| index-journal | ||
| index-query | ||
| index-reverse | ||
| lexicon | ||
| readme.md | ||
Index
These are components that offer functionality for the index-service.
Indexes
There are two indexes with accompanying tools for constructing them.
-
index-reverse is code for
word->documentindexes. There are two such indexes, one containing only document-word pairs that are flagged as important, e.g. the word appears in the title or has a high TF-IDF. This allows good results to be discovered quickly without having to sift through ten thousand bad ones first. -
index-forward is the
document->wordindex containing metadata about each word, such as its position. It is used after identifying candidate search results via the reverse index to fetch metadata and rank the results.
These indices rely heavily on the libraries/btree and libraries/array components.
Algorithms
- domain-ranking contains ranking algorithms.
Libraries
- index-query contains structures for evaluating search queries.
- index-journal contains tools for writing and reading index data.
- lexicon contains a mapping between words' string representation and an unique integer identifier.