where {application} is the application name, {table} is the perspective table to be queried, and {params} are URI parameters, separated by ampersands (&) and encoded as necessary. The following parameters are supported:
• q=text (required): A DQL query expression that defines which objects to select. Examples:
• s=size (optional): Limits the number of objects returned. If absent, the page size defaults to the search_default_page_size option in the doradus.yaml file. The page size can be set to 0 to disable paging, causing all results to be returned in a single page. Examples:
• f=fields (optional): A comma-separated list of fields to return for each selected object. Without this parameter, all scalar fields of each object are returned. Link paths can use parenthetical or dotted qualification. Link fields can use WHERE filtering and per-object value limits in square brackets. Examples:
• m=metric expression list (optional): A comma-separated list of metric expressions to be computed and returned for each selected objects. The syntax for metric expressions is the same as for aggregate queries. Examples:
• o=field [ASC|DESC] (optional): Orders the results by the specified field, which must be a scalar field belonging to the perspective table. Without this parameter, objects are returned in an internally-defined order. When an order field is specified, by default objects are sorted in ascending of the field’s value. Optionally, the field name can be followed by ASC to explicitly request ascending order or DESC to request descending order. Examples:
• k=count (optional): Causes the first count objects in the query results to be skipped. Without this parameter, the first page of objects is returned. Examples:
• g=token (optional): Returns a secondary page of objects starting with the first object greater than the given continuation token. The continuation token must be one returned in a previous query. The &g parameter can only be used for queries that are not sorted (no &o parameter). The &g and &e parameters cannot both be used in the same query.
• e=token (optional): Returns a secondary page of objects starting with the first object equal to the given continuation token. The continuation token must be one returned in a previous query. The &e parameter can only be used for queries that are not sorted (no &o parameter). The &g and &e parameters cannot both be used in the same query.
• shards=shards (required*): A comma-separated list of shard names. Only the specified shards are searched. Either this or the range parameter must be provided. Examples:
• range=shard-from[,shard-to] (required*): A starting shard name and optional ending shard name that defines the range of shards to search. If the ending shard-to name is omitted, all shards whose name is greater than or equal to the shard-from name are searched. Either this or the shards parameter must be provided, but not both. Examples:
• uncommitted=[true|false]: Indicates whether the query should include update batches that have not yet been merged in the selected shard(s). Setting this option to true causes the query to include all data batches. However, the results may be different than if the query was executed after the batches were merged. See the section Multi-shard and Uncommitted Data Queries.Query results can be paged using either of two methods depending on whether or not the results are sorted with the &o parameter:
• Sorted queries: To retrieve a secondary page, the same query text should be submitted along with the &k parameter to specify the number of objects to skip. Doradus OLAP will re-execute the query and skip the specified number of objects.
• Unsorted queries: To retrieve a secondary page, the same query text should be submitted using either the &g or &e parameter to pass the continuation token from the previous page. This form of paging is more efficient since Doradus OLAP does not re-execute the entire query but instead continues the query from the continuation object.The following object query selects people whose LastName is Powell and returns their full name, their manager's name, and their direct reports' name. The shard named 2014-01-01 is queried: