a discussion and choose a place
> > > >> where a
> > > >>>>>>>> "default query timeout" property will be configured.
> > > >>>>>>>>
> > > >>>>>>>> Gener
; >> for
> > >>>>>>>> queries to execute indefinitely. And I have no doubts that we
> > >> can
> > >>>>>>>> improve there. There could be several implementation
> > >> strategies. One
> > >>>>>>&
;>>>>>> is adding a property to CacheConfiguration. But it opens
> >> various
> >>>>>>>> questions. E.g. how should it work if we execute SQL JOIN
> >> spanning
> >>>>>>>> multiple tables (caches)? Also I a
;>> multiple tables (caches)? Also I am concerned about queries
>> executed
>>>>>>>> not via cache.query() method. We have multiple alternative
>> options,
>>>>>>>> e.g. thin clients (IgniteClient.query) or JDBC. I believe that
>>&g
; > > > > >
> > > > > > > > Hi Ivan,
> > > > > > > >
> > > > > > > > Thank you for your email. My understanding from the jira
> issue was
> > > > it
> > >
configuration for query default timeout.
> > > > > > >
> > > > > > > I need more info on the usage for this config property and if it
> > > > > > > is
> > > > > > shared
> > > > > > > in this jira issue I can make changes or if ther
; > > > issue
> > > > > > I can assign myself.
> > > > > >
> > > > > >
> > > > > > Regards,
> > > > > > Saikat
> > > > > >
> > > > > > On Mon, Apr 22, 2019 at
> > > > Regards,
> > > > > Saikat
> > > > >
> > > > > On Mon, Apr 22, 2019 at 5:31 AM Павлухин Иван >
> > > > wrote:
> > > > >
> > > > > > Hi Saikat,
> > > > > >
> > > > &g
; wrote:
> > > >
> > > > > Hi Saikat,
> > > > >
> > > > > I see that a configuration property is added in PR but I do not see
> > > > > how the property is used. Was it done intentionally?
> > > > >
> >
Was it done intentionally?
> > > >
> > > > Also, we need to decide whether such timeout should be configured per
> > > > cache or for all caches in one place. For example, we have already
> > > > TransactionConfiguration#setDefaultTxTimeout wh
he or for all caches in one place. For example, we have already
> > > TransactionConfiguration#setDefaultTxTimeout which is a global one.
> > >
> > > Share you thoughts.
> > >
> > > вс, 21 апр. 2019 г. в 00:38, Saikat Maitra
imeout should be configured per
> > cache or for all caches in one place. For example, we have already
> > TransactionConfiguration#setDefaultTxTimeout which is a global one.
> >
> > Share you thoughts.
> >
> > вс, 21 апр. 2019 г. в 00:38, Saikat Maitra :
> >
ould be configured per
> cache or for all caches in one place. For example, we have already
> TransactionConfiguration#setDefaultTxTimeout which is a global one.
>
> Share you thoughts.
>
> вс, 21 апр. 2019 г. в 00:38, Saikat Maitra :
> >
> > Hi,
> >
> > I h
#setDefaultTxTimeout which is a global one.
Share you thoughts.
вс, 21 апр. 2019 г. в 00:38, Saikat Maitra :
>
> Hi,
>
> I have raised a PR for the below issue.
>
> IGNITE-7285 Add default query timeout
>
> PR - https://github.com/apache/ignite/pull/6490
>
> Please
Hi,
I have raised a PR for the below issue.
IGNITE-7285 Add default query timeout
PR - https://github.com/apache/ignite/pull/6490
Please take a look and share feedback.
Regards,
Saikat
Valentin Kulichenko created IGNITE-7285:
---
Summary: Add default query timeout
Key: IGNITE-7285
URL: https://issues.apache.org/jira/browse/IGNITE-7285
Project: Ignite
Issue Type:
16 matches
Mail list logo
