Using range filters does not require Dgidx or dgraph configuration flags.
Range filters can be applied to either properties or dimensions of the following types:
Properties of type Numeric (Integer, Floating point, DateTime) or type Geocode
Dimensions of type Numeric that contain only Integer or Floating point values.
Note
Although dimensions do not have type, configuring a dimension's refinement sort order to be numeric causes the dimension to be treated as numeric in range filters, so long as all values can be parsed as integral or floating point values.
For values of properties and dimensions of type Floating point, you can specify values using both decimal (0.00...68), and scientific notation (6.8e-10).
Use Developer Studio to configure the appropriate property type. For example, the following property is configured to be of type Floating point:
Running queries with range filtering on dimensions is done with the same
Nf parameter that is used for queries with range
filtering on properties.
For example, this is a query with a range filter on a dimension. In this example, the name of the dimension is ContainsDigit and the records are numbers:
N=0&Nf=ContainsDigit|GT+8
This query returns all numbers that contain values greater than 8. As the example shows, running a query with a range filter on a dimension makes sense only for dimensions with values of type Integer or Floating Point.
No Dgidx flags are necessary to enable range filters. All range filter computational work is done at request-time.
Likewise, no MDEX Engine configuration flags are necessary to enable range filters. All numeric properties and dimensions and all geocode properties are automatically enabled for use in range filters.
