Opaque bookmark token used when paginating results.
A boolean value that indicates whether or not to include information about existing conflicts in the document.
Path parameter to specify the database name.
Use this option to find information about the query that was run. This information includes total key
lookups, total document lookups (when include_docs=true
is used), and total quorum document lookups (when each
document replica is fetched).
JSON array that uses the field syntax. Use this parameter to specify which fields of a document must be returned. If it is omitted, the entire document is returned.
Maximum number of results returned. The type: text
indexes are limited to 200 results when queried.
Path parameter to specify the database partition key.
JSON object describing criteria used to select documents. The selector specifies fields in the document, and provides an expression to evaluate with the field content or other data.
The selector object must:
Using a selector is significantly more efficient than using a JavaScript filter function, and is the recommended option if filtering on document attributes only.
Elementary selector syntax requires you to specify one or more fields, and the corresponding values required for those fields. You can create more complex selector expressions by combining operators.
Operators are identified by the use of a dollar sign $
prefix in the name field.
There are two core types of operators in the selector syntax:
$and
, $or
, $not
, $nor
) there are three combination operators:
$all
, $elemMatch
, and $allMatch
. A combination operator takes a single argument. The argument is either
another selector, or an array of selectors.$eq
operator matches when the specified field contains a value that is equal to the
supplied argument.$eq
, $gt
, $gte
, $lt
, and $lte
(but not $ne
) can be used as the
basis of a query. You should include at least one of these in a selector.For further reference see selector syntax.
Skip the first 'n' results, where 'n' is the value that is specified.
The sort field contains a list of pairs, each mapping a field name to a sort direction (asc or desc). The first field name and direction pair is the topmost level of sort. The second pair, if provided, is the next level of sort. The field can be any field, using dotted notation if desired for sub-document fields.
For example in JSON: [{"fieldName1": "desc"}, {"fieldName2.subFieldName1": "desc"}]
When sorting with multiple fields, ensure that there is an index already defined with all the sort fields in the same order and each object in the sort array has a single key or at least one of the sort fields is included in the selector. All sorting fields must use the same sort direction, either all ascending or all descending.
Whether or not the view results should be returned from a "stable" set of shards.
Whether to update the index prior to returning the result.
Use this option to identify a specific index for query to run against, rather than by using the IBM Cloudant Query algorithm to find the best index.
Generated using TypeDoc
Parameters for the
postPartitionFind
operation.