lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-7039) Improve PointRangeQuery & co
Date Sat, 20 Feb 2016 14:38:18 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Muir updated LUCENE-7039:
--------------------------------
    Attachment: LUCENE-7039.patch

Here is a prototype patch.

> Improve PointRangeQuery & co
> ----------------------------
>
>                 Key: LUCENE-7039
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7039
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>         Attachments: LUCENE-7039.patch
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message