| Name |
Description |
Links |
| Term Vector support |
|
|
| Support for Search Term Highlighting |
|
|
| Better support for hits sorted by things other
than score. |
An easy, efficient case is to support results
sorted by the order documents were
added to the index. A little harder and less efficient is support
for
results sorted by an arbitrary field.
|
|
| Add some requested methods: Document.getValues,
IndexReader.getIndexedFields |
String[] Document.getValues(String
fieldName);
String[] IndexReader.getIndexedFields();
void Token.setPositionIncrement(int); |
|
| Add lastModified() method to Directory,
FSDirectory and RamDirectory, so it could be cached in IndexWriter/Searcher
manager. |
|
|
| Support for adding more than 1 term to the same
position. |
N.B. I think the Finnish lady already
implemented this. It required some pieces of Lucene to be modified. (OG). |
|
| The ability to retrieve the number of occurrences
not only for a term but also for a Phrase. |
|
|
| A lady from Finland submitted code for handling
Finnish. |
| Dutch stemmer, analyzer, etc. |
|
|
| French stemmer, analyzer, etc. |
|
|
| Che Dong's CJKTokenizer for Chinese, Japanese,
and Korean. |
|
|
| Selecting a language-specific analyzer according
to a locale. |
Now we rewrite parts of Lucene code in order
to use another analyzer. It will be useful to select analyzer without
touching code. |
|
| Adding "-encoding" option and encoding-sensitive
methods to tools. |
Current tools needs minor changes on a
Japanese (and other language) environment: adding an "-encode" option and
argument, using Reader/Writer classes instead of InputStream/OutputStream
classes, etc. |
|
