[ https://issues.apache.org/jira/browse/IGNITE-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172964#comment-17172964 ]
Taras Ledkov commented on IGNITE-13183: --------------------------------------- [~korlov], [~amashenkov] please review the patch. > Query timeout redesign > ---------------------- > > Key: IGNITE-13183 > URL: https://issues.apache.org/jira/browse/IGNITE-13183 > Project: Ignite > Issue Type: Improvement > Components: sql > Affects Versions: 2.8.1 > Reporter: Taras Ledkov > Assignee: Taras Ledkov > Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > *Motivation:* > Now the query timeout is set up for each node separately by the node > configuration. This property isn't propagated for the all nodes of cluster. > Also user cannot change / disable query timeout without restart all nodes of > the cluster. > *Proposal fix:* > - Adds the default query timeout property to the > {{DistributedSqlConfiguration}}. Use distributed metastore to store and > manage the property. > - Deprecates the {{SqlConfiguration#defaultQueryTimeout}} property and use it > to set up initial value of new property > {{DistributedSqlConfiguration#defaultQueryTimeout}} > - Adds info about explicit query timeout to {{GridH2QueryRequest}} (boolean > flag {{explicitTimeout=false}} by default). This is necessary so that the > default timeout may be used for queries from old nodes. > - When query timeout is set to zero by old node ({{explicitTimeout=false}}) > we assume this is the default value and use default timeout for this queries. -- This message was sent by Atlassian Jira (v8.3.4#803005)