[
https://issues.apache.org/jira/browse/IGNITE-19748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-19748:
---------------------------------------
Description:
We can set timeout for SQL queries:
* Using {{SqlFieldsQuery.timeout}} property (for certain query)
* Using "sql.defaultQueryTimeout" distributed property (default for all queries)
But Calcite-based SQL query engine ignore these timeouts. Only possible timeout
supported by the new engine is planning timeout. We should support execution
timeouts too.
was:
We can set timeout for SQL queries:
* Using {{SqlFieldsQuery.timeout}} property (for certain query)
* Using "sql.defaultQueryTimeout" distributed property (default for all queries)
But Calcite-based SQL query engine ignore these timeouts. Only possible timeout
supported by the new engine is planning timeout. We should support execution
timeouts too.
> Calcite engine. Support queries timeout
> ---------------------------------------
>
> Key: IGNITE-19748
> URL: https://issues.apache.org/jira/browse/IGNITE-19748
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite
>
> We can set timeout for SQL queries:
> * Using {{SqlFieldsQuery.timeout}} property (for certain query)
> * Using "sql.defaultQueryTimeout" distributed property (default for all
> queries)
> But Calcite-based SQL query engine ignore these timeouts. Only possible
> timeout supported by the new engine is planning timeout. We should support
> execution timeouts too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
