[
https://issues.apache.org/jira/browse/IGNITE-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-5651.
-------------------------------------
Resolution: Won't Fix
Not an issue. We already have timeout flag, which is used for query cancel. We
should not mix different things into one:
- timeout is a tool for users
- warnings are for both users and admins to track cluster healtth
That said, it is perfectly valid to print a warning even when big timeout is
set.
> Add long query timeout property
> -------------------------------
>
> Key: IGNITE-5651
> URL: https://issues.apache.org/jira/browse/IGNITE-5651
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.0
> Reporter: Alexander Paschenko
> Priority: Major
>
> It would be nice to allow users setting long execution timeout when sending a
> query - by doing so, user won't start getting dull long execution warnings
> which may be well expected. Instead, they will set their own acceptable
> timeout and will start seeing warnings only when they want to.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
