The score comments only refer to this test, not to the global query engine.
Filtering is allowed and we can implement it, I don't see the value of having that specific condition in the test as long as we can't control the output of the 'score' function. So what I did is I only removed the test condition that was referring to the score's value: "and score() >= 0.0".
From the lucene docs:
> You can always pick an arbitrary score value and then check the Hits object to see how many results have a score higher than that value (a Binary search might come in handy) but it really doesn't give you any meaningful information because of the way score is calculated
From our oak code :
> // TODO if score() is not supported by the index, use the value 0.0?
So as long as we don't know what the output is, what sense does it make to test against "0"?
Also are there any test in jackrabbit that have where conditions based on the score output?