Description
If a point range matches most documents and every document has exactly one value, then we could make things faster by computing the set of documents that do NOT match the range instead.
It was not possible until recently since figuring out whether a range query matches most documents was not possible, but we can now use the new PointValues.estimatePointcount API to do that: we could just check whether the cost of the inverse visitor is lower than the cost of the regular range visitor.