 |
Page History
...
A simple query consists of the following parts:
- attribute or attributeMatch
- value
- operator
- levelFilter
- attributeMatch
- (optional)
When you perform a query, the system requires it in the context of a compoundQuery element, even if it is only one simple query. A A compound query consists of the following parts:
- Join operator
- List of simple queries (filtering criteria)
- List of compound queries (filtering criteria)
- Additional optional indicators
A compoundQuery element should A compound query should at least have one simple query that could be part of a list of queries or a list of nested compound queries.
...
The following table describes the additional indicators to consider in your querycompoundQuery element:
| Indicator | Description |
|---|---|
| detailedResponse | By default, the search returns only the path of matched resulted collections. If |
| the query specifies true for the detailedResponse indicator, the service returns collections with metadata. |
| page |
| By default, the query returns the first 100 results in page 1, the second 100 in page 2, and so on. If |
| the query omits the page indicator, the |
| service fetches page 1. If the query specifies a number for the page indicator, the service returns the specified page of results. | |
| totalCount | If |
| the query specifies true for the totalCount indicator, the service returns a total count of collections matching the query regardless of the query limit and page. The default for this indicator is false, so if |
| the query omits it, |
| the service does not return a total count. |
