Apache Solr - RangeQuery

RangeQuery appears to be a range query that operates on strings.  I'm not sure if it only works on strings or if the strings are a way for it to auto-determine what field type it's going to work with.

If you know how to properly use this, please leave a comment below.  I'm stumped on this one.

Fields

• fieldName (required in hierarchy here or a parent)
• lowerTerm - string value
• upperTerm - string value
• includeLower (optional, default true)
• includeUpper (optional, default true)

Examples

Simply paste the following into the q= field in the Admin UI.

Here's a query that I came up with, but it doesn't work as I'd expect.

{!xmlparser}

<RangeQuery

 fieldName="price"

 lowerTerm="1.00"

 upperTerm="3.00"

 includeLower="true"

 includeUpper="true">

</RangeQuery>

The above query returns no results, which isn't what I was expecting.

{!xmlparser}

<RangeQuery

 fieldName="price"

 lowerTerm="0"

 upperTerm="10.00"

 includeLower="true"

 includeUpper="true">

</RangeQuery>

The above query returns 30 documents, of which includes prices > 10.00, which isn't what I expected.

Apache Solr - LegacyNumericRangeQuery

NumericRangeQuery was renamed to LegacyNumericRangeQuery about lucene 6.0.0 and marked deprecated. If you're on an older system, you will find it using NumericRangeQuery. Afterwards, LegacyNumericRangeQuery will be what you will want to use.

It looks like NumericRangeQuery has been replaced with PointRangeQuery.

Fields

• fieldName (required here or in a parent node)
• lowerTerm (optional, default null)
• upperTerm (optional, default null)
• includeLower (optional, default true)
• includeUpper (optional, default true)
• precisionStep (optional, default 16)
• type (optional, default "int") - long | int | double | float

Examples

Simply paste the following into the q= field in the Admin UI.

NOTE: These examples will not work in Solr since Solr does not support Point types.

Lucene 6.0.0+:

{!xmlparser}

<LegacyNumericRangeQuery

 fieldName="price"

 lowerTerm="0"

 upperTerm="10"

 includeLower="true"

 includeUpper="true"

 precisionStep="16"

 type="float">

</LegacyNumericRangeQuery>

Before Lucene 6.0.0:

{!xmlparser}

<NumericRangeQuery

 fieldName="price"

 lowerTerm="0"

 upperTerm="10"

 includeLower="true"

 includeUpper="true"

 precisionStep="16"

 type="float">

</NumericRangeQuery>

Apache Solr - PointRangeQuery

PointRangeQuery is new as of about Apache Solr 6.0 and is meant to replace the, now deprecated, NumericRangeQuery (which got renamed to LegacyNumericRangeQuery).

NOTE: The following may be confusing, and here's why.  The PointRangeQueryBuilder, used by XmlQueryParser, requires that lowerTerm and upperTerm are specified, which means that neither of them may default.  However, in the code, it covers its bases in case lowerTerm or upperTerm was not specified.  In these cases, it defaults to the MIN_VALUE and MAX_VALUE for the respective types.  Until the code is updated after 6.0.0, the defaults cannot be reached.  If you are reading this after they become optional, the following may be beneficial to you.  Until then, you will be required to enter a value for both.

Fields

• fieldName (required in hierarchy here or in a parent node)
• lowerTerm (required)
• upperTerm (required)
• type (optional, default "int") - long | int | double | float
• long
• If lowerTerm is not specified, default to Long.MIN_VALUE (-9223372036854775808)
• If upperTerm is not specified, default to Long.MAX_VALUE (9223372036854775807)
• int
• If lowerTerm is not specified, default to Integer.MIN_VALUE (-2147483648)
• If upperTerm is not specified, default to Integer.MAX_VALUE (2147483647)
• double
• If lowerTerm is not specified, default to Double.NEGATIVE_INFINITY
• If upperTerm is not specified, default to Double.POSITIVE_INFINITY
• float
• If lowerTerm is not specified, default to Float.NEGATIVE_INFINITY
• If upperTerm is not specified, default to Float.POSITIVE_INFINITY

Example

Simply paste the following into the q= field in the Admin UI.

NOTE: This example should work, but it doesn't in my Solr 6.0.0 build because Point types aren't supported in Solr yet.  I do know that the PointRangeQuery code is running when I submit this query, because it gives me error messages when I don't specify required parameters.  However, somewhere in between, something isn't supported and no documents are returned.  Please leave a comment if you know more.

{!xmlparser}

<PointRangeQuery

 fieldName="price"

 lowerTerm="0.00"

 upperTerm="100.00"

 type="float">

</PointRangeQuery>