| cost_based_optimization | If false, disables the cost-based optimization of the given query. The default value is false. The supported values are: |
| distributed_joins | If true, enables the use of distributed joins in servicing the given query. Any query requiring a distributed join will succeed, though hints can be used in the query to change the distribution of the source data to allow the query to succeed. The default value is false.
The supported values are: |
| distributed_operations | If true, enables the use of distributed operations in servicing the given query. Any query requiring a distributed join will succeed, though hints can be used in the query to change the distribution of the source data to allow the query to succeed. The default value is
false. The supported values are: |
| ignore_existing_pk | Specifies the record collision error-suppression policy for inserting into or updating a table with a primary key, only used when primary key record collisions are rejected (update_on_existing_pk is false). If set to true, any
record insert/update that is rejected for resulting in a primary key collision with an existing table record will be ignored with no error generated. If false, the rejection of any insert/update for resulting in a primary key collision will cause an error to be reported. If
the specified table does not have a primary key or if update_on_existing_pk is true, then this option has no effect. The default value is false. | Supported
Values | Description |
|---|
| true | Ignore inserts/updates that result in primary key collisions with existing records | | false | Treat as errors any inserts/updates that result in primary key collisions with existing records |
|
| late_materialization | If true, Joins/Filters results will always be materialized ( saved to result tables format) The default value is false. The supported values are: |
| paging_table | When empty or the specified paging table not exists, the system will create a paging table and return when query output has more records than the user asked. If the paging table exists in the system, the records from the paging table are returned without evaluating the query. |
| paging_table_ttl | Sets the TTL of the paging table. |
| parallel_execution | If false, disables the parallel step execution of the given query. The default value is true. The supported values are: |
| plan_cache | If false, disables plan caching for the given query. The default value is true. The supported values are: |
| prepare_mode | If true, compiles a query into an execution plan and saves it in query cache. Query execution is not performed and an empty response will be returned to user The default value is false. The supported values are: |
| preserve_dict_encoding | If true, then columns that were dict encoded in the source table will be dict encoded in the projection table. The default value is true. The supported values are: |
| query_parameters | Query parameters in JSON array or arrays (for inserting multiple rows). This can be used instead of input parameter data and input parameter request_schema_str. |
| results_caching | If false, disables caching of the results of the given query The default value is true. The supported values are: |
| rule_based_optimization | If false, disables rule-based rewrite optimizations for the given query The default value is true. The supported values are: |
| ssq_optimization | If false, scalar subqueries will be translated into joins The default value is true. The supported values are: |
| ttl | Sets the TTL of the intermediate result tables used in query execution. |
| update_on_existing_pk | Specifies the record collision policy for inserting into or updating a table with a primary key. If set to true, any existing table record with primary key values that match those of a record being inserted or updated will be
replaced by that record. If set to false, any such primary key collision will result in the insert/update being rejected and the error handled as determined by ignore_existing_pk. If the specified table does not have a primary key, then this option has no effect. The
default value is false. | Supported
Values | Description |
|---|
| true | Replace the collided-into record with the record inserted or updated when a new/modified record causes a primary key collision with an existing record | | false | Reject the insert or update when it results in a primary key collision with an existing record |
|
| validate_change_column | When changing a column using alter table, validate the change before applying it. If true, then validate all values. A value too large (or too long) for the new type will prevent any change. If false, then when a value is too large or long, it will be truncated. The default
value is true. The supported values are: |
| current_schema | Use the supplied value as the default schema when processing this SQL command. |
