Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
New
Description
The point types are now preferred for indexing numeric fields, but PointRangeQuery has some usability issues.
I think we should make the following changes:
- newIntRange(), newLongRange(), newFloatRange(),newDoubleRange(), newBinaryRange(): simple 1D ranges consistent with NumericRangeQuery naming.
- newMultiIntRange(), newMultiLongRange(), newMultiFloatRange(), newMultiDoubleRange(), newMultiBinaryRange(): multi-dimensional versions of the above (take arrays, a bit harder to use, but the arrays have correct type!)
- toString() should be meaningful, it should not spew binary nonsense unless you used a binary range!
- improve javadocs
If we like this, we could do similar improvements for the ExactPointQuery