MarkLogic Server 11.0 Product Documentationcts.elementAttributeRangeQuery
cts.elementAttributeRangeQuery( element-name as xs.QName[], attribute-name as xs.QName[], operator as String, value as (String | Number | Boolean | null | Array | Object)[], [options as String[]], [weight as Number?] ) as cts.elementAttributeRangeQuery
Summary
Constructs a query that matches element-attributes by name with a range-index entry equal to a given value. An element attribute range index on the specified QName(s) must exist when you use this query in a search; if no such range index exists, the search throws an exception.
Usage Notes
To constrain on a range of values, combine multiple element attribute
range queries together using
cts.andQuery or another
composable query constructor.
If neither "cached" nor "uncached" is present, it specifies "cached".
The "cached-incremental" option can improve performance if you repeatedly perform range queries on date or dateTime values over a short range that does not vary widely over short period of time. To benefit, the operator should remain the same "direction" (<,<=, or >,>=) across calls, the bounding date or dateTime changes slightly across calls, and the query runs very frequently (multiple times per minute). Note that using this options creates significantly more cached queries than the "cached" option.
The "cached-incremental" option has the following restrictions and interactions: The "min-occurs" and "max-occurs" options will be ignored if you use "cached-incremental" in unfiltered search. You can only use "score-function=zero" with "cached-incremental". The "cached-incremental" option behaves like "cached" if you are not querying date or dateTime values.
Negative "min-occurs" or "max-occurs" values will be treated as 0 and non-integral values will be rounded down. An error will be raised if the "min-occurs" value is greater than the "max-occurs" value.
"score-function=linear" means that values that are further away from the bounds will score higher. "score-function=reciprocal" means that values that are closer to the bounds will score higher. The functions are scaled appropriately for different types, so that in general the default slope factor will provide useful results. Using a slope factor greater than 1 gives distinct scores over a smaller range of values, and produces generally higher scores. Using a slope factor less than 1 gives distinct scores over a wider range of values, and produces generally lower scores.
For queries against a dateTime index, when $value is an xs:dayTimeDuration or xs:yearMonthDuration, the query is executed as an age query. $value is subtracted from fn:current-dateTime() to create an xs:dateTime used in the query. If there is more than one item in $value, they must all be the same type.
Example
// Insert some test data of the following form:
// <entry sku="N"/>
declareUpdate();
xdmp.documentInsert('/attribute1.xml',
(new NodeBuilder())
.startElement('entry')
.addAttribute('sku','100')
.endElement()
.toNode()) ;
xdmp.documentInsert('/attribute2.xml',
(new NodeBuilder())
.startElement('entry')
.addAttribute('sku','200')
.endElement()
.toNode()) ;
xdmp.documentInsert('/attribute3.xml',
(new NodeBuilder())
.startElement('entry')
.addAttribute('sku','1000')
.endElement()
.toNode()) ;
// *************************************************
// In a separate query, search the test data. This search
// requires an attribute (range) index of type xs:int on the
// "sku" attribute of the "entry" element
cts.search(
cts.elementAttributeRangeQuery(
xs.QName("entry"), xs.QName("sku"), ">=",
500));
// Returns the following document (with URI "/attribute3.xml"):
// <?xml version="1.0" encoding="UTF-8"?>
// <entry sku="1000"></entry>