cts:element-attribute-range-query
cts:element-attribute-range-query(
$element-name as xs:QName*,
$attribute-name as xs:QName*,
$operator as xs:string,
$value as xs:anyAtomicType*,
[$options as xs:string*],
[$weight as xs:double?]
) as cts:element-attribute-range-query
Summary
Returns a cts:query
matching element-attributes by name with a
range-index entry equal to a given value. Searches with the
cts:element-attribute-range-query
constructor require an attribute range index on the specified QName(s);
if there is no range index configured, then an exception is thrown.
Parameters |
element-name |
One or more element QNames to match.
When multiple QNames are specified,
the query matches if any QName matches.
|
attribute-name |
One or more attribute QNames to match.
When multiple QNames are specified,
the query matches if any QName matches.
|
operator |
A comparison operator.
Operators include:
- "<"
- Match range index values less than $value.
- "<="
- Match range index values less than or equal to $value.
- ">"
- Match range index values greater than $value.
- ">="
- Match range index values greater than or equal to $value.
- "="
- Match range index values equal to $value.
- "!="
- Match range index values not equal to $value.
|
value |
Some values to match.
When multiple values are specified,
the query matches if any value matches.
|
options |
Options to this query. The default is ().
Options include:
- "collation=URI"
- Use the range index with the collation specified by
URI. If not specified, then the default collation
from the query is used. If a range index with the specified
collation does not exist, an error is thrown.
- "cached"
- Cache the results of this query in the list cache.
- "uncached"
- Do not cache the results of this query in the list cache.
- "min-occurs=number"
- Specifies the minimum number of occurrences required. If
fewer that this number of words occur, the fragment does not match.
The default is 1.
- "max-occurs=number"
- Specifies the maximum number of occurrences required. If
more than this number of words occur, the fragment does not match.
The default is unbounded.
- "score-function=function"
- Use the selected scoring function. The score function may be:
- linear
- Use a linear function of the difference between the
specified query value and the matching value in the index to calculate
a score for this range query.
- reciprocal
- Use a reciprocal function of the difference
between the specified query value and the matching value in the
index to calculate a score for this range query.
- zero
- This range query does not contribute to the
score. This is the default.
- "slope-factor=number"
- Apply the given number as a scaling factor to the slope of the
scoring function. The default is 1.0.
- "synonym"
- Specifies that all of the terms in the $value parameter are
considered synonyms for scoring purposes. The result is that
occurrences of more than one of the synonyms are scored as if
there are more occurrences of the same term (as opposed to
having a separate term that contributes to score).
|
weight |
A weight for this query. The default is 1.0.
|
Usage Notes
If you want to constrain on a range of values, you can combine multiple
cts:element-attribute-range-query
constructors together
with cts:and-query
or other composable cts:query
constructors.
If neither "cached" nor "uncached" is present, it specifies "cached".
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.
Example
(: create a document with test data :)
xdmp:document-insert("/attributes.xml",
<root>
<entry sku="100">
<product>apple</product>
</entry>
<entry sku="200">
<product>orange</product>
</entry>
<entry sku="1000">
<product>electric car</product>
</entry>
</root>) ;
(:
requires an attribute (range) index of
type xs:int on the "sku" attribute of
the "entry" element
:)
cts:search(doc("/attributes.xml")/root/entry,
cts:element-attribute-range-query(
xs:QName("entry"), xs:QName("sku"), ">=",
500))
(:
returns the following node:
<entry sku="1000">
<product>electric car</product>
</entry>
:)
Stack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.