org.apache.lucene.analysis.ar.ArabicLetterTokenizer
|
org.apache.lucene.analysis.ar.ArabicLetterTokenizerFactory
(3.1) Use StandardTokenizerFactory instead.
|
org.apache.lucene.analysis.cn.ChineseAnalyzer
(3.1) Use StandardAnalyzer instead, which has the same functionality.
This analyzer will be removed in Lucene 5.0
|
org.apache.lucene.analysis.cn.ChineseFilter
(3.1) Use StopFilter instead, which has the same functionality.
This filter will be removed in Lucene 5.0
|
org.apache.lucene.analysis.cn.ChineseFilterFactory
|
org.apache.lucene.analysis.cn.ChineseTokenizer
(3.1) Use StandardTokenizer instead, which has the same functionality.
This filter will be removed in Lucene 5.0
|
org.apache.lucene.analysis.cn.ChineseTokenizerFactory
|
org.apache.lucene.analysis.cjk.CJKTokenizer
Use StandardTokenizer, CJKWidthFilter, CJKBigramFilter, and LowerCaseFilter instead.
|
org.apache.lucene.analysis.cjk.CJKTokenizerFactory
|
org.apache.lucene.collation.CollationKeyFilter
|
org.apache.lucene.collation.CollationKeyFilterFactory
|
org.apache.lucene.analysis.nl.DutchStemFilter
|
org.apache.lucene.analysis.nl.DutchStemmer
(3.1) Use DutchStemmer instead,
which has the same functionality. This filter will be removed in Lucene 5.0
|
org.apache.lucene.analysis.fr.FrenchStemFilter
|
org.apache.lucene.analysis.fr.FrenchStemmer
Use FrenchStemmer instead,
which has the same functionality. This filter will be removed in Lucene 4.0
|
org.apache.lucene.analysis.in.IndicTokenizer
|
org.apache.lucene.analysis.ngram.Lucene43EdgeNGramTokenizer |
org.apache.lucene.analysis.ngram.Lucene43NGramTokenizer |
org.apache.lucene.analysis.miscellaneous.Lucene47WordDelimiterFilter |
org.apache.lucene.analysis.miscellaneous.PatternAnalyzer
(4.0) use the pattern-based analysis in the analysis/pattern package instead.
|
org.apache.lucene.analysis.position.PositionFilter
(4.4) PositionFilter makes TokenStream graphs inconsistent
which can cause highlighting bugs. Its main use-case being to make
QueryParser
generate boolean queries instead of phrase queries, it is now advised to use
QueryParser.setAutoGeneratePhraseQueries(boolean)
(for simple cases) or to override QueryParser.newFieldQuery .
|
org.apache.lucene.analysis.position.PositionFilterFactory
(4.4)
|
org.apache.lucene.analysis.ru.RussianLetterTokenizer
(3.1) Use StandardTokenizer instead, which has the same functionality.
This filter will be removed in Lucene 5.0
|
org.apache.lucene.analysis.ru.RussianLetterTokenizerFactory
|
org.apache.lucene.analysis.snowball.SnowballAnalyzer
(3.1) Use the language-specific analyzer in modules/analysis instead.
This analyzer will be removed in Lucene 5.0
|
org.apache.lucene.analysis.standard.std31.StandardTokenizerImpl31 |
org.apache.lucene.analysis.standard.std34.StandardTokenizerImpl34 |
org.apache.lucene.analysis.standard.std40.StandardTokenizerImpl40 |
org.apache.lucene.analysis.th.ThaiWordFilter
|
org.apache.lucene.analysis.th.ThaiWordFilterFactory
|
org.apache.lucene.analysis.standard.std31.UAX29URLEmailTokenizerImpl31 |
org.apache.lucene.analysis.standard.std34.UAX29URLEmailTokenizerImpl34 |
org.apache.lucene.analysis.standard.std36.UAX29URLEmailTokenizerImpl36 |
org.apache.lucene.analysis.standard.std40.UAX29URLEmailTokenizerImpl40 |