Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Set Query Options

  • how-to
    +
    You can use the query options to change the query timeout period, define request-level parameters, and so on.

    Prerequisites

    To use the Enterprise Analytics UI, you need the Enterprise Analytics Access role along with specific privileges.

    Access Query Settings

    You can specify various query options by clicking the Settings icon at the top right corner. This opens the Run-Time Preferences menu.

    Available Query Options

    When you select query options, you can define the following settings and request-level parameters and click Save Preferences to save the configuration.

    • Query Timeout

    • Collect query timings

    • Scan Consistency

    • Positional Parameters

    • Named Parameters

    Descriptions of these settings follow.

    Query Timeout Setting

    You define a query timeout to specify the maximum time, in seconds, for the system to spend on a query before timing out.

    This setting has a default value of 1800 with 1 being the lowest value.

    Collect Query Timings

    To collect per-operator query timings during query execution and display them in the query plan, click Collect query timings. By default, this option is not selected.

    Scan Consistency Setting

    The scan consistency setting specifies the consistency guarantee for scanning. You can select 1 of the following options:

    • not_bounded: The scan does not use a timestamp vector. This is the fastest mode, because it avoids the costs of obtaining the vector.

    • request_plus: This option implements bounded consistency. Before processing the request, a current vector is obtained. The vector is used as a lower bound for the statements in the request.

    Positional Parameters

    Positional parameters use numeric identifiers to represent values to supply in a query. Enterprise Analytics automatically supplies numbered identifiers for these parameters as you add them: $1, $2, and so on. The value you enter must use JSON formatting, such as enclosing strings in quotation marks.

    To add positional parameters, click the + button. To remove parameters from last to first, click the - button.

    Example

    You define the following positional parameters:

    $1 "Paris"
$2 "Gare du Nord"

    When you run the following query:

    SELECT * FROM travel-sample.inventory.airport
WHERE airportname <> $2 AND city = $1;

    The result returns the 8 documents that have "Paris" as the city but that do not have "Gare du Nord" as the airport name.

    You can then reuse these parameters in other queries as is, change their values, or delete them.

    Named Parameters

    Named parameters store an identifying variable name in addition to the value. The name must start with $, and the value must use JSON formatting, such as enclosing strings in quotation marks.

    To add named parameters, click the + button. To remove parameters from last to first, click the - button.

    Example

    You define a parameter, $n, and specify a value of "Orbit Airlines" for it.

    When you run the following query:

    SELECT * FROM travel-sample.inventory.airport
WHERE name = $n;

    The result returns the single document that has an airline name of "Orbit Airlines".

    You can then reuse $n in other queries as is, change its value, update its name, or delete it.

    See Also