Deprecated Methods |
it.unimi.dsi.mg4j.query.parser.SimpleCharStream.getColumn()
|
it.unimi.dsi.mg4j.query.parser.SimpleCharStream.getLine()
|
it.unimi.dsi.mg4j.index.AbstractIndexIterator.iterator()
|
it.unimi.dsi.mg4j.search.IntervalIterator.next()
As of MG4J 1.2, the suggested way of iterating over interval iterators
is IntervalIterator.nextInterval() , which has been reintroduced with a fully lazy semantics.
After a couple of releases, however, this annotation will be removed, as it
is very practical to have interval iterators implementing Iterator<Interval> . Its
main purpose is to warn people about performance issues solved by IntervalIterator.nextInterval() . |
it.unimi.dsi.mg4j.search.AbstractDocumentIterator.AbstractIntervalIterator.next()
|
it.unimi.dsi.mg4j.search.DocumentIterator.nextInt()
As of MG4J 1.2, the suggested way of iterating over document iterators
is DocumentIterator.nextDocument() , which has been modified so to provide fully lazy
iteration. After a couple of releases, however, this annotation will be removed, as it
is very practical to have document iterators implementing IntIterator . Its
main purpose is to warn people about performance issues solved by DocumentIterator.nextDocument() . |
it.unimi.dsi.mg4j.search.AbstractDocumentIterator.nextInt()
|
it.unimi.dsi.mg4j.search.score.AbstractScorer.nextInt()
|
it.unimi.dsi.mg4j.search.score.Scorer.nextInt()
As of MG4J 1.2, the suggested way of iterating over scorer
is Scorer.nextDocument() , which provides fully lazy
iteration. After a couple of releases, however, this annotation will be removed, as it
is very practical to have scorers implementing IntIterator . Its
main purpose is to let people know about Scorer.nextDocument() , which solves
the same issues as DocumentIterator.nextDocument() . |
it.unimi.dsi.mg4j.document.InputStreamDocumentSequence.reset()
|