[jira] [Updated] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.
[
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-12316:
-
Reviewer: Dmitriy Govorukhin (was: Stepachev Maksim)
> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while
> evaluating *Forbidden operation inside transaction*
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11722) Batch BPlustTree updates for cache batch operations
[ https://issues.apache.org/jira/browse/IGNITE-11722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11722: - Labels: iep-16 (was: ) > Batch BPlustTree updates for cache batch operations > --- > > Key: IGNITE-11722 > URL: https://issues.apache.org/jira/browse/IGNITE-11722 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Semen Boikov >Priority: Major > Labels: iep-16 > > Now cache batch operations (putAll, invokeAll, removeAll) update BPlustTree > entries one by one. It makes sense to support batch updates in BPlustTree > and use it for cache batch operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11722) Batch BPlustTree updates for cache batch operations
[ https://issues.apache.org/jira/browse/IGNITE-11722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11722: - Labels: iep-16 iep-32 (was: iep-16) > Batch BPlustTree updates for cache batch operations > --- > > Key: IGNITE-11722 > URL: https://issues.apache.org/jira/browse/IGNITE-11722 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Semen Boikov >Priority: Major > Labels: iep-16, iep-32 > > Now cache batch operations (putAll, invokeAll, removeAll) update BPlustTree > entries one by one. It makes sense to support batch updates in BPlustTree > and use it for cache batch operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11765) Vulnerable library H2 Database Engine1.4.197 used
[ https://issues.apache.org/jira/browse/IGNITE-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968299#comment-16968299 ] Andrey Mashenkov commented on IGNITE-11765: --- This ticket was closed as the issue doesn't affect Ignite. See discussion on dev-list for details. > Vulnerable library H2 Database Engine1.4.197 used > - > > Key: IGNITE-11765 > URL: https://issues.apache.org/jira/browse/IGNITE-11765 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: VIJAY BHATT >Priority: Major > > We use blackduck for scanning our project. It has identified Ignite 2.7.0 > using H2 Database Engine version 1.4.197 as a vulnerable library having the > following 2 vulnerabilities: > BDSA-2018-1048 (CVE-2018-10054) > BDSA-2018-2507 (CVE-2018-14335) > Suggested fix by blackduck is to use version 1.4.198 > We tried using 1.4.198 using jar override but it has some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.
[
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-12316:
-
Reviewer: Stepachev Maksim (was: Ivan Rakov)
> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while
> evaluating *Forbidden operation inside transaction*
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-7935) Add batch update operation to PageMemory and Persistence
[ https://issues.apache.org/jira/browse/IGNITE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-7935: - Description: Updating each key-value pair independently is very inefficient when data arrives in batches (examples: cache.putAll(...), dataStreamer, preloading). Our internal data structures (B+ tree, FreeList) can be used more efficiently. (was: _Work on improving BPlusTree is being done in another ticket._ The performance of batch operations in Ignite can be improved by implementing batch updates on page memory level. We should add support for batch inserting data rows into FreeList and use it in batch operations to load data through preloader, dataStreamer, and cache.putAll(...).) > Add batch update operation to PageMemory and Persistence > > > Key: IGNITE-7935 > URL: https://issues.apache.org/jira/browse/IGNITE-7935 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ilya Lantukh >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-16, iep-32 > > Updating each key-value pair independently is very inefficient when data > arrives in batches (examples: cache.putAll(...), dataStreamer, preloading). > Our internal data structures (B+ tree, FreeList) can be used more > efficiently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7935) Add batch update operation to PageMemory and Persistence
[ https://issues.apache.org/jira/browse/IGNITE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-7935: - Summary: Add batch update operation to PageMemory and Persistence (was: Support batch updates in FreeList) > Add batch update operation to PageMemory and Persistence > > > Key: IGNITE-7935 > URL: https://issues.apache.org/jira/browse/IGNITE-7935 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ilya Lantukh >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-16, iep-32 > > _Work on improving BPlusTree is being done in another ticket._ > The performance of batch operations in Ignite can be improved by implementing > batch updates on page memory level. We should add support for batch inserting > data rows into FreeList and use it in batch operations to load data through > preloader, dataStreamer, and cache.putAll(...). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11765) Vulnerable library H2 Database Engine1.4.197 used
[ https://issues.apache.org/jira/browse/IGNITE-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11765: -- Ignite Flags: (was: Docs Required) > Vulnerable library H2 Database Engine1.4.197 used > - > > Key: IGNITE-11765 > URL: https://issues.apache.org/jira/browse/IGNITE-11765 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: VIJAY BHATT >Priority: Major > > We use blackduck for scanning our project. It has identified Ignite 2.7.0 > using H2 Database Engine version 1.4.197 as a vulnerable library having the > following 2 vulnerabilities: > BDSA-2018-1048 (CVE-2018-10054) > BDSA-2018-2507 (CVE-2018-14335) > Suggested fix by blackduck is to use version 1.4.198 > We tried using 1.4.198 using jar override but it has some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12351) Append additional cp tracking activity - pages sort.
[
https://issues.apache.org/jira/browse/IGNITE-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968184#comment-16968184
]
Ignite TC Bot commented on IGNITE-12351:
{panel:title=Branch: [pull/7036/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4749388buildTypeId=IgniteTests24Java8_RunAll]
> Append additional cp tracking activity - pages sort.
>
>
> Key: IGNITE-12351
> URL: https://issues.apache.org/jira/browse/IGNITE-12351
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Malinovskiy
>Assignee: Vladimir Malinovskiy
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CheckpointMetricsTracker has no info about _splitAndSortCpPagesIfNeeded_
> stage, thus in case of huge number of dirty pages someone can observe in log:
> 10:08:00 checkpoint started
> 10:10:00 checkpoint finished
> <--- ??
> 10:10:20 checkpoint started
> if checkpointFrequency = 3 and all tracker durations: beforeLockDuration,
> lockWaitDuration gives no clue what kind of work (20 sec) Checkpointer thread
> is waiting for.
> Additionally (hope this is not big deal) need t obe fixed redundant
> effectivePageId computation cause FullPageId already has effectivePageId info.
>
> {{return Long.compare(PageIdUtils.effectivePageId(o1.pageId()),
> PageIdUtils.effectivePageId(o2.pageId()));}}
> writeCheckpointEntr() duration should also be logged.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-6982) .NET: Migrate to latest NUnit
[ https://issues.apache.org/jira/browse/IGNITE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Shapkin updated IGNITE-6982: - Fix Version/s: (was: 2.4) 2.9 > .NET: Migrate to latest NUnit > - > > Key: IGNITE-6982 > URL: https://issues.apache.org/jira/browse/IGNITE-6982 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Alexandr Shapkin >Priority: Major > Labels: .NET > Fix For: 2.9 > > > We use very old NUnit 2.6. In order to reuse tests under .NET Core > (IGNITE-2662) we need latest NUnit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6982) .NET: Migrate to latest NUnit
[ https://issues.apache.org/jira/browse/IGNITE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968410#comment-16968410 ] Alexandr Shapkin commented on IGNITE-6982: -- [~ptupitsyn], deal, I will check it. > .NET: Migrate to latest NUnit > - > > Key: IGNITE-6982 > URL: https://issues.apache.org/jira/browse/IGNITE-6982 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Alexandr Shapkin >Priority: Major > Labels: .NET > Fix For: 2.9 > > > We use very old NUnit 2.6. In order to reuse tests under .NET Core > (IGNITE-2662) we need latest NUnit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6982) .NET: Migrate to latest NUnit
[ https://issues.apache.org/jira/browse/IGNITE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968393#comment-16968393 ] Pavel Tupitsyn commented on IGNITE-6982: [~ashapkin] let's make sure it is possible to see realtime console output both on TeamCity and in VS/Rider - this is very important, and this is what stopped me from migrating before. > .NET: Migrate to latest NUnit > - > > Key: IGNITE-6982 > URL: https://issues.apache.org/jira/browse/IGNITE-6982 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Alexandr Shapkin >Priority: Major > Labels: .NET > Fix For: 2.9 > > > We use very old NUnit 2.6. In order to reuse tests under .NET Core > (IGNITE-2662) we need latest NUnit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6982) .NET: Migrate to latest NUnit
[ https://issues.apache.org/jira/browse/IGNITE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968389#comment-16968389 ] Alexandr Shapkin commented on IGNITE-6982: -- [~ptupitsyn] I think it's time to review this issue. Probably we could benefit from the new parallel test execution concept. > .NET: Migrate to latest NUnit > - > > Key: IGNITE-6982 > URL: https://issues.apache.org/jira/browse/IGNITE-6982 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.4 > > > We use very old NUnit 2.6. In order to reuse tests under .NET Core > (IGNITE-2662) we need latest NUnit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-6982) .NET: Migrate to latest NUnit
[ https://issues.apache.org/jira/browse/IGNITE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Shapkin reopened IGNITE-6982: -- Ignite Flags: Release Notes Required Assignee: Alexandr Shapkin (was: Pavel Tupitsyn) > .NET: Migrate to latest NUnit > - > > Key: IGNITE-6982 > URL: https://issues.apache.org/jira/browse/IGNITE-6982 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Alexandr Shapkin >Priority: Major > Labels: .NET > Fix For: 2.4 > > > We use very old NUnit 2.6. In order to reuse tests under .NET Core > (IGNITE-2662) we need latest NUnit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12352) Add default query timeout .NET
[
https://issues.apache.org/jira/browse/IGNITE-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12352:
---
Description:
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.
It is related to https://issues.apache.org/jira/browse/IGNITE-7285
was: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.
> Add default query timeout .NET
> ---
>
> Key: IGNITE-12352
> URL: https://issues.apache.org/jira/browse/IGNITE-12352
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.3
>Reporter: Saikat Maitra
>Priority: Minor
>
> 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.
>
> It is related to https://issues.apache.org/jira/browse/IGNITE-7285
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968918#comment-16968918
]
Saikat Maitra commented on IGNITE-7285:
---
[~ptupitsyn]
As discussed I have updated the PR and removed the .NET changes.
I have also created a separate issue for .NET changes
https://issues.apache.org/jira/browse/IGNITE-12352
Regards,
Saikat
> 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: 10h 20m
> 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
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968927#comment-16968927
]
Saikat Maitra commented on IGNITE-7285:
---
[~Pavlukhin]
I have updated the PR and replied on your comments. Please take a look.
If the changes looks good from this issue's scope perspective then we can merge
this PR and take up additional changes in separate Jira issue and PR.
Let me know your thoughts?
Regards,
Saikat
> 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: 10.5h
> 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
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12352) Add default query timeout .NET
[
https://issues.apache.org/jira/browse/IGNITE-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12352:
---
Affects Version/s: 2.3
> Add default query timeout .NET
> ---
>
> Key: IGNITE-12352
> URL: https://issues.apache.org/jira/browse/IGNITE-12352
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.3
>Reporter: Saikat Maitra
>Priority: Major
>
> 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
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12352) Add default query timeout .NET
[
https://issues.apache.org/jira/browse/IGNITE-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12352:
---
Priority: Minor (was: Major)
> Add default query timeout .NET
> ---
>
> Key: IGNITE-12352
> URL: https://issues.apache.org/jira/browse/IGNITE-12352
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.3
>Reporter: Saikat Maitra
>Priority: Minor
>
> 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
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12352) Add default query timeout .NET
[
https://issues.apache.org/jira/browse/IGNITE-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12352:
---
Description: 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.
> Add default query timeout .NET
> ---
>
> Key: IGNITE-12352
> URL: https://issues.apache.org/jira/browse/IGNITE-12352
> Project: Ignite
> Issue Type: Improvement
>Reporter: Saikat Maitra
>Priority: Major
>
> 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
(v8.3.4#803005)
[jira] [Created] (IGNITE-12352) Add default query timeout .NET
Saikat Maitra created IGNITE-12352: -- Summary: Add default query timeout .NET Key: IGNITE-12352 URL: https://issues.apache.org/jira/browse/IGNITE-12352 Project: Ignite Issue Type: Improvement Reporter: Saikat Maitra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12352) Add default query timeout .NET
[
https://issues.apache.org/jira/browse/IGNITE-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12352:
---
Component/s: sql
> Add default query timeout .NET
> ---
>
> Key: IGNITE-12352
> URL: https://issues.apache.org/jira/browse/IGNITE-12352
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Saikat Maitra
>Priority: Major
>
> 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
(v8.3.4#803005)
