ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Pavlukhin (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7285) Add default query timeout
Date Tue, 20 Aug 2019 20:53:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911725#comment-16911725

Ivan Pavlukhin commented on IGNITE-7285:

Hi [~samaitra],

I suspect that not all places where a timeout should be passed are covered yet. For me it
looks more natural to calculate a query timeout (taking default one into account) upon {{QueryParameters}}
initialization. It is worth to consider following points for an implementation:
1. Reduce a number of places where _default timeout_ is read from configuration (ideally there
should be only one place).
2. Be able to disable a timeout for a particular query ({{SqlFieldsQuery.setTimeout(0)}})
when default non-zero timeout is configured.

> Add default query timeout
> -------------------------
>                 Key: IGNITE-7285
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7285
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache, sql
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Saikat Maitra
>            Priority: Major
>              Labels: sql-stability
>             Fix For: 2.8
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
> Currently it's possible to provide timeout only on query level. It would be very useful
to have default timeout value provided on cache startup. Let's add {{CacheConfiguration#defaultQueryTimeout}}
configuration property.

This message was sent by Atlassian Jira

View raw message