Alas, this is a bug in CustomScoreQuery. I've opened this:
https://issues.apache.org/jira/browse/LUCENE-2190
With Lucene 2.9, we now search one segment at a time. So the rollback
to 0 that you're seeing is in fact due to a new segment being
searched. We need to fix CustomScoreQuery to notify
Hello,
I'm trying to use the doc parameter to build a customScore, but the 'doc'
value seems to be different from the global 'docId' when the index is not
optimized.
Basically, I create a DateScoreQuery passing the IndexReader and the field
containing the timestamp (as long)
And I use t
