There was a bug in the LogMergePolicy that was surfacing when there were
segments, but all of the segments were larger than the max limit.
After filtering, the list of segments candidate for merge was 0, and
the code was indexing the first element of an empty Vec.
* Add offset to TopDocsCollector
Add an offset to TopDocsCollector and TopDocs to make it clearer how to
handle pagination.
Closes#822
* Address review comments
- Make Debug formatting of TopDocs clearer.
- Add unit tests for limit and offset on TopCollector.
- Change API for using offset to a fluent interface.
- Add some context to the docstring to clarify what limit and offset are
equivalent to in other projects.
* Changes required by rebase on e25284
- Pass Collector into TweakedScoreTopCollector and
CustomScoreTopCollector.
- Add std:: qualifier to f32, i32 etc. Not sure why this was not failing
already.
- Add unit tests for TopDocs with offset including for tweaked and
custom score collectors.
In order to convert a TopCollector<Score> to a TopCollector<TScore> I
had to add a `into_tscore` method to `TopCollector`. This is a hack but
I don't know how to avoid it.
- Change in the DocSet and Scorer API. (@fulmicoton).
A freshly created DocSet point directly to their first doc. A sentinel value called TERMINATED marks the end of a DocSet.
`.advance()` returns the new DocId. `Scorer::skip(target)` has been replaced by `Scorer::seek(target)` and returns the resulting DocId.
As a result, iterating through DocSet now looks as follows
```rust
let mut doc = docset.doc();
while doc != TERMINATED {
// ...
doc = docset.advance();
}
```
The change made it possible to greatly simplify a lot of the docset's code.
- Misc internal optimization and introduction of the `Scorer::for_each_pruning` function. (@fulmicoton)
* Make TweakScore and CustomScore mutable
Make TweakScore and CustomScore mutable at the segment level.
Addresses issue #806
* Add example to show tweak_score working for facets
When applying the delete operations in the delete queue, it is possible
that there was no new deleted document.
In this case, avoid creating a new delete file, and updating the delete
opstamp.
* Alternative take on boosted queries
* Fixing unit test
* Added boosting to the query grammar.
* Made BoostQuery public.
* Added support for boosting field in QueryParser
Closes#547
