[jira] [Commented] (IGNITE-21886) Refactor CompressionProcessorImpl, move code partially to ignite-core module
[
https://issues.apache.org/jira/browse/IGNITE-21886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834146#comment-17834146
]
Ignite TC Bot commented on IGNITE-21886:
{panel:title=Branch: [pull/11290/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11290/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 5{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7812312]]
* {color:#013220}IgnitePdsTestSuite5:
WalPageRecordCompactionTest.testWalPageCompaction - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7812357buildTypeId=IgniteTests24Java8_RunAll]
> Refactor CompressionProcessorImpl, move code partially to ignite-core module
>
>
> Key: IGNITE-21886
> URL: https://issues.apache.org/jira/browse/IGNITE-21886
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CompressionProcessorImpl contains some logic, which can be used without extra
> dependencies. For example, all page compaction logic implemented in
> ignite-core, but we still can't enable SKIP_GARBAGE compression mode without
> ignite-compress module.
> Mode SKIP_GARBAGE without extra dependencies can be helpful for WAL page
> snapshot compression or for IGNITE-20697.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21929) Skip pending list extra cleanup in TTL Manager
[
https://issues.apache.org/jira/browse/IGNITE-21929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834138#comment-17834138
]
Ignite TC Bot commented on IGNITE-21929:
{panel:title=Branch: [pull/11300/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11300/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7812865]]
* {color:#013220}IgniteBinaryCacheTestSuite:
GridCacheTtlManagerSelfTest.testReplicatedRemove - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
GridCacheTtlManagerSelfTest.testPartitionedRemove - PASSED{color}
{color:#8b}Cache 10{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7812866]]
* {color:#013220}IgniteCacheTestSuite10:
GridCacheTtlManagerLoadTest.testPartitionedRemove - PASSED{color}
* {color:#013220}IgniteCacheTestSuite10:
GridCacheTtlManagerLoadTest.testReplicatedRemove - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7812967buildTypeId=IgniteTests24Java8_RunAll]
> Skip pending list extra cleanup in TTL Manager
> --
>
> Key: IGNITE-21929
> URL: https://issues.apache.org/jira/browse/IGNITE-21929
> Project: Ignite
> Issue Type: Improvement
>Reporter: Yuri Naryshkin
>Assignee: Yuri Naryshkin
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently when records expire with high rate, several threads (sys-stripe,
> client-connector) try to cleanup those records and get stuck waiting to
> acquire lock on main page of PendingEntriesTree. This is unnecessary
> contention.
> After introducing fix for IGNITE-14341 expired records PendingEntriesTree
> cleanup is done using range. After that each record is deleted from dataTree.
> And after that another attempt is done to remove each record from
> PendingEntriesTree once again, which is not necessary as the record is
> already removed.
> This ticket is to improve cleaning up expired entries by skipping second
> attempt to remove each record from PendingEntriesTree.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21099) .NET: Thin 3.0: Ensure AOT compatibility
[ https://issues.apache.org/jira/browse/IGNITE-21099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21099: Description: Ensure that Ignite.NET library is AOT-compatible: https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ To test this: * Run existing tests in AOT mode? Not sure if NUnit can do that. * Write separate tests to check basic functionality for AOT * See https://devblogs.microsoft.com/dotnet/testing-your-native-aot-dotnet-apps/ (note: experimental, closed-source testing framework) was: Ensure that Ignite.NET library is AOT-compatible: https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ To test this: * Run existing tests in AOT mode? Not sure if NUnit can do that. * Write separate tests to check basic functionality for AOT * See https://devblogs.microsoft.com/dotnet/testing-your-native-aot-dotnet-apps/ > .NET: Thin 3.0: Ensure AOT compatibility > > > Key: IGNITE-21099 > URL: https://issues.apache.org/jira/browse/IGNITE-21099 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > > Ensure that Ignite.NET library is AOT-compatible: > https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ > To test this: > * Run existing tests in AOT mode? Not sure if NUnit can do that. > * Write separate tests to check basic functionality for AOT > * See > https://devblogs.microsoft.com/dotnet/testing-your-native-aot-dotnet-apps/ > (note: experimental, closed-source testing framework) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21099) .NET: Thin 3.0: Ensure AOT compatibility
[ https://issues.apache.org/jira/browse/IGNITE-21099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21099: Description: Ensure that Ignite.NET library is AOT-compatible: https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ To test this: * Run existing tests in AOT mode? Not sure if NUnit can do that. * Write separate tests to check basic functionality for AOT * See https://devblogs.microsoft.com/dotnet/testing-your-native-aot-dotnet-apps/ was: Ensure that Ignite.NET library is AOT-compatible: https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ To test this: * Run existing tests in AOT mode? Not sure if NUnit can do that. * Write separate tests to check basic functionality for AOT > .NET: Thin 3.0: Ensure AOT compatibility > > > Key: IGNITE-21099 > URL: https://issues.apache.org/jira/browse/IGNITE-21099 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > > Ensure that Ignite.NET library is AOT-compatible: > https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/ > To test this: > * Run existing tests in AOT mode? Not sure if NUnit can do that. > * Write separate tests to check basic functionality for AOT > * See > https://devblogs.microsoft.com/dotnet/testing-your-native-aot-dotnet-apps/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21990) [PerfStat] Report can skip properties/rows/reads records from remote nodes
Aleksey Plekhanov created IGNITE-21990: -- Summary: [PerfStat] Report can skip properties/rows/reads records from remote nodes Key: IGNITE-21990 URL: https://issues.apache.org/jira/browse/IGNITE-21990 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov In IGNITE-21863 after processing "query" record, we store aggregated result, assuming that after this point there are no more records related to this query. But such records may exist in other files (from other nodes). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21145) Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.*
[ https://issues.apache.org/jira/browse/IGNITE-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21145: -- Fix Version/s: 2.17 > Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.* > > > Key: IGNITE-21145 > URL: https://issues.apache.org/jira/browse/IGNITE-21145 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 40m > Remaining Estimate: 0h > > Delete all classes from: > 1) org/apache/ignite/internal/processors/cache/tree/mvcc/data > * MvccCacheIdAwareDataInnerIO > * MvccCacheIdAwareDataLeafIO > * MvccDataInnerIO > * MvccDataLeafIO > * MvccDataRow > * MvccUpdateDataRow > * MvccUpdateResult > * ResultType > 2) org/apache/ignite/internal/processors/cache/tree/mvcc/search > * MvccDataPageClosure > * MvccFirstRowTreeClosure > * MvccLinkAwareSearchRow > * MvccMaxSearchRow > * MvccMinSearchRow > * MvccSearchRow > * MvccSnapshotSearchRow > * MvccTreeClosure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21628) Transactional SQL commands removal
[
https://issues.apache.org/jira/browse/IGNITE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-21628:
--
Fix Version/s: 2.17
> Transactional SQL commands removal
> --
>
> Key: IGNITE-21628
> URL: https://issues.apache.org/jira/browse/IGNITE-21628
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL commands should be removed:
> * {{BEGIN [TRANSACTION]}} -> {{SqlBeginTransactionCommand}}
> * {{COMMIT [TRANSACTION]}} -> {{SqlCommitTransactionCommand}}
> * {{ROLLBACK [TRANSACTION]}} -> {{SqlRollbackTransactionCommand}}
> * {{SELECT FOR UPDATE}}
> * etc.
> All corresponding parsing code should be removed too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21987) Optimize RO scan in sorted indexes
[ https://issues.apache.org/jira/browse/IGNITE-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis reassigned IGNITE-21987: -- Assignee: Philipp Shergalis > Optimize RO scan in sorted indexes > -- > > Key: IGNITE-21987 > URL: https://issues.apache.org/jira/browse/IGNITE-21987 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > This issue applies to aimem/aipersist primarily. Optimization for rocksdb > might be done separately. > * add new method to SortedIndexStorage, like "readOnlyScan", that returns a > simple cursor > * in the implementation we should use alternative cursor implementation for > RO scans - it should delegate calls to B+Tree cursor > * reuse existing tests where possible > * call new method where necessary (PartitionReplicaListener#scanSortedIndex) > IMPORTANT: we should throw an exception if somebody scans an index and > IndexStorage#getNextRowIdToBuild is not null. It should be a new error, like > "IndexNotBuiltException" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21987) Optimize RO scan in sorted indexes
[ https://issues.apache.org/jira/browse/IGNITE-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21987: --- Description: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new method to SortedIndexStorage, like "readOnlyScan", that returns a simple cursor * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor * reuse existing tests where possible * call new method where necessary (PartitionReplicaListener#scanSortedIndex) IMPORTANT: we should throw an exception if somebody scans an index and IndexStorage#getNextRowIdToBuild is not null. It should be a new error, like "IndexNotBuiltException" was: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new method to SortedIndexStorage, like "readOnlyScan", that returns a simple cursor * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor * reuse existing tests where possible * call new method where necessary (PartitionReplicaListener#scanSortedIndex) IMPORTANT: we should throw an exception if somebody scans an index and IndexStorage#getNextRowIdToBuild is not null. > Optimize RO scan in sorted indexes > -- > > Key: IGNITE-21987 > URL: https://issues.apache.org/jira/browse/IGNITE-21987 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > This issue applies to aimem/aipersist primarily. Optimization for rocksdb > might be done separately. > * add new method to SortedIndexStorage, like "readOnlyScan", that returns a > simple cursor > * in the implementation we should use alternative cursor implementation for > RO scans - it should delegate calls to B+Tree cursor > * reuse existing tests where possible > * call new method where necessary (PartitionReplicaListener#scanSortedIndex) > IMPORTANT: we should throw an exception if somebody scans an index and > IndexStorage#getNextRowIdToBuild is not null. It should be a new error, like > "IndexNotBuiltException" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21987) Optimize RO scan in sorted indexes
[ https://issues.apache.org/jira/browse/IGNITE-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21987: --- Description: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new method to SortedIndexStorage, like "readOnlyScan", that returns a simple cursor * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor * reuse existing tests where possible * call new method where necessary (PartitionReplicaListener#scanSortedIndex) IMPORTANT: we should throw an exception if somebody scans an index and IndexStorage#getNextRowIdToBuild is not null. was: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new method to SortedIndexStorage, like "readOnlyScan", that returns a simple cursor * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor * reuse existing tests where possible * call new method where necessary (PartitionReplicaListener#scanSortedIndex) > Optimize RO scan in sorted indexes > -- > > Key: IGNITE-21987 > URL: https://issues.apache.org/jira/browse/IGNITE-21987 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > This issue applies to aimem/aipersist primarily. Optimization for rocksdb > might be done separately. > * add new method to SortedIndexStorage, like "readOnlyScan", that returns a > simple cursor > * in the implementation we should use alternative cursor implementation for > RO scans - it should delegate calls to B+Tree cursor > * reuse existing tests where possible > * call new method where necessary (PartitionReplicaListener#scanSortedIndex) > IMPORTANT: we should throw an exception if somebody scans an index and > IndexStorage#getNextRowIdToBuild is not null. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21988) Don't allow reading from index storage if it is in build state
Kirill Tkalenko created IGNITE-21988: Summary: Don't allow reading from index storage if it is in build state Key: IGNITE-21988 URL: https://issues.apache.org/jira/browse/IGNITE-21988 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 3.0.0-beta2 We need to prohibit read operations from *org.apache.ignite.internal.storage.index.IndexStorage* if they are in build state. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21987) Optimize RO scan in sorted indexes
[ https://issues.apache.org/jira/browse/IGNITE-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21987: --- Description: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new method to SortedIndexStorage, like "readOnlyScan", that returns a simple cursor * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor * reuse existing tests where possible * call new method where necessary (PartitionReplicaListener#scanSortedIndex) was: This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new flag RO_SCAN to SortedIndexStorage * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor, and "peek" should throw an "UnsupportedOperationException" * for "rocksdb" it shouldn't refresh the iterator all the time. "peek" should also throw exceptions * reuse existing tests * pass new RO_SCAN flag into a method where it's necessary > Optimize RO scan in sorted indexes > -- > > Key: IGNITE-21987 > URL: https://issues.apache.org/jira/browse/IGNITE-21987 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > This issue applies to aimem/aipersist primarily. Optimization for rocksdb > might be done separately. > * add new method to SortedIndexStorage, like "readOnlyScan", that returns a > simple cursor > * in the implementation we should use alternative cursor implementation for > RO scans - it should delegate calls to B+Tree cursor > * reuse existing tests where possible > * call new method where necessary (PartitionReplicaListener#scanSortedIndex) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21989) JDBC URL completer uses outdated topology
Vadim Pakhnushev created IGNITE-21989:
-
Summary: JDBC URL completer uses outdated topology
Key: IGNITE-21989
URL: https://issues.apache.org/jira/browse/IGNITE-21989
Project: Ignite
Issue Type: Improvement
Components: cli
Reporter: Vadim Pakhnushev
Assignee: Vadim Pakhnushev
{{JdbcUrlRegistryImpl}} uses {{NodeNameRegistry}} in order to get all nodes
URLs. These registries are updated periodically and it so happens that the
order is {{JdbcUrlRegistry}} then {{NodeNameRegistry}} so {{JdbcUrlRegistry}}
always uses outdated topology information.
For example, after the first connect valid JDBC URL completion happens only
after second update which by default happens every 5 seconds.
When node leaves the cluster, this could lead to unwanted delays in updates
where {{JdbcUrlRegistry}} tries to connect to the already left node.
This was found when running the
{{ItIgnitePicocliCommandsTest#startStopNodeWhenCompleteNodeName}} on Windows,
where connect attempt takes a lot of time if the node is stopped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21987) Optimize RO scan in sorted indexes
Ivan Bessonov created IGNITE-21987: -- Summary: Optimize RO scan in sorted indexes Key: IGNITE-21987 URL: https://issues.apache.org/jira/browse/IGNITE-21987 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov This issue applies to aimem/aipersist primarily. Optimization for rocksdb might be done separately. * add new flag RO_SCAN to SortedIndexStorage * in the implementation we should use alternative cursor implementation for RO scans - it should delegate calls to B+Tree cursor, and "peek" should throw an "UnsupportedOperationException" * for "rocksdb" it shouldn't refresh the iterator all the time. "peek" should also throw exceptions * reuse existing tests * pass new RO_SCAN flag into a method where it's necessary -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21926) The status of GridCacheLockImpl and GridCacheSemaphoreImpl may be inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-21926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833936#comment-17833936
]
Vyacheslav Koptilin commented on IGNITE-21926:
--
Hi [~yexiaowei] ,
Could you please share a test that demonstrates the issue? It would be nice to
add it to the patch.
> The status of GridCacheLockImpl and GridCacheSemaphoreImpl may be inconsistent
> --
>
> Key: IGNITE-21926
> URL: https://issues.apache.org/jira/browse/IGNITE-21926
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: yexiaowei
>Priority: Major
>
> I noticed that GridCacheLockImpl and GridCacheSemaphoreImpl can cause
> deadlocks. Because their model is similar to the following
> {code:java}
> Sync sync;
>
> void init() {
> sync = getSync();
> }
>
> void onUpdate(val) {
> if(sync == null) {
> return;
> }
> update(sync);
> }
> {code}
> If init and onUpdate occur at the same time, update may be missed and lagging
> data may be obtained. The fix I gave is similar to:
> {code:java}
> Sync sync;
> boolean flag = false;
>
> void init() {
> do {
> flag = false;
> s = getSync();
> } while(flag);
> }
>
> void onUpdate(val) {
> if(sync == null) {
> flag = true;
> return;
> }
> update(sync);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21307) Call failure handler in case of failure in WatchProcessor
[
https://issues.apache.org/jira/browse/IGNITE-21307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833934#comment-17833934
]
Denis Chudov commented on IGNITE-21307:
---
[~slava.koptilin] LGTM.
> Call failure handler in case of failure in WatchProcessor
> -
>
> Key: IGNITE-21307
> URL: https://issues.apache.org/jira/browse/IGNITE-21307
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For the linearized watch processing, we have
> WatchProcessor#notificationFuture that is rewritten for each revision
> processing and meta storage safe time advance. If some watch processor
> completes exceptionally, this means that no further updates will be
> processed, because they need the previous updates to be processed
> successfully. This is implemented in futures chaining like this:
>
> {code:java}
> notificationFuture = notificationFuture
> .thenRunAsync(() -> revisionCallback.onSafeTimeAdvanced(time),
> watchExecutor)
> .whenComplete((ignored, e) -> {
> if (e != null) {
> LOG.error("Error occurred when notifying safe time advanced
> callback", e);
> }
> }); {code}
> For now, we dont have any failure handing of exceptionally completed
> notification future. It leads to the endless log records with the same
> exception's stack trace, caused by meta storage safe time advances:
>
> {code:java}
> [2024-01-16T21:42:35,515][ERROR][%isot_n_0%JRaft-FSMCaller-Disruptor-metastorage-_stripe_0-0][WatchProcessor]
> Error occurred when notifying safe time advanced callback
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.lang.IgniteInternalException: IGN-CMN-65535
> TraceId:3877e098-6a1b-4f30-88a8-a4c13411d573 Peers are not ready
> [groupId=5_part_0]
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1081)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> Caused by: org.apache.ignite.internal.lang.IgniteInternalException: Peers are
> not ready [groupId=5_part_0]
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:725)
> ~[ignite-raft-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:709)
> ~[ignite-raft-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:234)
> ~[ignite-raft-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:190)
> ~[ignite-raft-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.start(TopologyAwareRaftGroupService.java:187)
> ~[ignite-replicator-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupServiceFactory.startRaftGroupService(TopologyAwareRaftGroupServiceFactory.java:73)
> ~[ignite-replicator-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.raft.Loza.startRaftGroupService(Loza.java:350)
> ~[ignite-raft-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$startPartitionAndStartClient$27(TableManager.java:917)
> ~[ignite-table-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.util.IgniteUtils.inBusyLock(IgniteUtils.java:827)
> ~[ignite-core-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$startPartitionAndStartClient$28(TableManager.java:913)
> ~[ignite-table-9.0.127-SNAPSHOT.jar:?]
> at
> java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> ~[?:?]
> ... 4 more {code}
> So, the node can't operate properly and just produces tons of logs. Such
> nodes should be halted.
> UPD:
> We decided to just add invocation of {{failureProcessor.process}} in all
> places in {{org.apache.ignite.internal.metastorage.server.WatchProcessor}}
> where exceptions happen, like
> {code:java}
>
[jira] [Created] (IGNITE-21986) Sql. Create planner test for TPCH queries.
Andrey Mashenkov created IGNITE-21986: - Summary: Sql. Create planner test for TPCH queries. Key: IGNITE-21986 URL: https://issues.apache.org/jira/browse/IGNITE-21986 Project: Ignite Issue Type: Test Reporter: Andrey Mashenkov IGNITE-21580 introduced a new tests to validate TPC-h query uses optimal query plans. Let's make the same for the others TPC-h tests and make `TpchQueryPlannerTest` test parameterized. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21907) Change thread count for RAFT disruptors to improve performance
[
https://issues.apache.org/jira/browse/IGNITE-21907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833913#comment-17833913
]
Vladislav Pyatkov commented on IGNITE-21907:
Merged 58f43c8f058f40f1ec5eaad44c6f69ca5a17aa9d
> Change thread count for RAFT disruptors to improve performance
> --
>
> Key: IGNITE-21907
> URL: https://issues.apache.org/jira/browse/IGNITE-21907
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. Motivation
> Right now, we use a stripe count to configure count of thread. The default
> number of threads is double the number of processors.
> {code:java|title=NodeOptions.java}
> private static final int DEFAULT_STRIPES = Utils.cpus() * 2;
> {code}
> The total number of threads is more than enough. Our throughput tests showed
> that a lower number of treads leads to better performance.
> h3. Definition of done
> Default stripes couint is _Utils.cpus()_
> Default number of stripes for RAFT log manager is _4_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21985) Extend test coverage for SQL T624(Common logarithm functions)
Iurii Gerzhedovich created IGNITE-21985: --- Summary: Extend test coverage for SQL T624(Common logarithm functions) Key: IGNITE-21985 URL: https://issues.apache.org/jira/browse/IGNITE-21985 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL T621(Enhanced numeric functions) is poor. Let's increase the test coverage. ref - test/sql/function/numeric/test_pg_math.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21985) Extend test coverage for SQL T624(Common logarithm functions)
[ https://issues.apache.org/jira/browse/IGNITE-21985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21985: Description: Test coverage for SQL T624(Common logarithm functions) is poor. Let's increase the test coverage. ref - test/sql/function/numeric/test_pg_math.test was: Test coverage for SQL T621(Enhanced numeric functions) is poor. Let's increase the test coverage. ref - test/sql/function/numeric/test_pg_math.test > Extend test coverage for SQL T624(Common logarithm functions) > - > > Key: IGNITE-21985 > URL: https://issues.apache.org/jira/browse/IGNITE-21985 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL T624(Common logarithm functions) is poor. > Let's increase the test coverage. > > ref - test/sql/function/numeric/test_pg_math.test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21984) Extend test coverage for SQL T621(Enhanced numeric functions)
[ https://issues.apache.org/jira/browse/IGNITE-21984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21984: Description: Test coverage for SQL T621(Enhanced numeric functions) is poor. Let's increase the test coverage. ref - test/sql/function/numeric/test_pg_math.test was: Test coverage for SQL T031(BOOLEAN data type) is poor. Let's increase the test coverage. ref - test_boolean_cast.test > Extend test coverage for SQL T621(Enhanced numeric functions) > - > > Key: IGNITE-21984 > URL: https://issues.apache.org/jira/browse/IGNITE-21984 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL T621(Enhanced numeric functions) is poor. > Let's increase the test coverage. > > ref - test/sql/function/numeric/test_pg_math.test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21984) Extend test coverage for SQL T621(Enhanced numeric functions)
Iurii Gerzhedovich created IGNITE-21984: --- Summary: Extend test coverage for SQL T621(Enhanced numeric functions) Key: IGNITE-21984 URL: https://issues.apache.org/jira/browse/IGNITE-21984 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL T031(BOOLEAN data type) is poor. Let's increase the test coverage. ref - test_boolean_cast.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21983) Extend test coverage for SQL T031(BOOLEAN data type)
[ https://issues.apache.org/jira/browse/IGNITE-21983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21983: Description: Test coverage for SQL T031(BOOLEAN data type) is poor. Let's increase the test coverage. ref - test_boolean_cast.test was: Test coverage for SQL T021(BINARY and VARBINARY data types) is poor. Let's increase the test coverage. ref - test/sql/types/blob/test_blob_cast.test > Extend test coverage for SQL T031(BOOLEAN data type) > > > Key: IGNITE-21983 > URL: https://issues.apache.org/jira/browse/IGNITE-21983 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL T031(BOOLEAN data type) is poor. > Let's increase the test coverage. > > ref - test_boolean_cast.test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21983) Extend test coverage for SQL T031(BOOLEAN data type)
Iurii Gerzhedovich created IGNITE-21983: --- Summary: Extend test coverage for SQL T031(BOOLEAN data type) Key: IGNITE-21983 URL: https://issues.apache.org/jira/browse/IGNITE-21983 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL T021(BINARY and VARBINARY data types) is poor. Let's increase the test coverage. ref - test/sql/types/blob/test_blob_cast.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21982) Extend test coverage for SQL T021(BINARY and VARBINARY data types)
[ https://issues.apache.org/jira/browse/IGNITE-21982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21982: Description: Test coverage for SQL T021(BINARY and VARBINARY data types) is poor. Let's increase the test coverage. ref - test/sql/types/blob/test_blob_cast.test was: Test coverage for SQL F862( in subqueries) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_correlated_subquery_cte.test > Extend test coverage for SQL T021(BINARY and VARBINARY data types) > -- > > Key: IGNITE-21982 > URL: https://issues.apache.org/jira/browse/IGNITE-21982 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL T021(BINARY and VARBINARY data types) is poor. > Let's increase the test coverage. > > ref - test/sql/types/blob/test_blob_cast.test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21982) Extend test coverage for SQL T021(BINARY and VARBINARY data types)
Iurii Gerzhedovich created IGNITE-21982: --- Summary: Extend test coverage for SQL T021(BINARY and VARBINARY data types) Key: IGNITE-21982 URL: https://issues.apache.org/jira/browse/IGNITE-21982 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F862( in subqueries) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_correlated_subquery_cte.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21981) Extend test coverage for SQL F862( in subqueries)
Iurii Gerzhedovich created IGNITE-21981: --- Summary: Extend test coverage for SQL F862( in subqueries) Key: IGNITE-21981 URL: https://issues.apache.org/jira/browse/IGNITE-21981 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F861(Top-level in ) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21981) Extend test coverage for SQL F862( in subqueries)
[ https://issues.apache.org/jira/browse/IGNITE-21981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21981: Description: Test coverage for SQL F862( in subqueries) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_correlated_subquery_cte.test was: Test coverage for SQL F861(Top-level in ) is poor. Let's increase the test coverage. > Extend test coverage for SQL F862( in subqueries) > --- > > Key: IGNITE-21981 > URL: https://issues.apache.org/jira/browse/IGNITE-21981 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F862( in subqueries) is poor. > Let's increase the test coverage. > > ref - test/sql/subquery/scalar/test_correlated_subquery_cte.test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21980) Extend test coverage for SQL F861(Top-level in )
[ https://issues.apache.org/jira/browse/IGNITE-21980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21980: Description: Test coverage for SQL F861(Top-level in ) is poor. Let's increase the test coverage. was: Test coverage for SQL F781(Self-referencing operations) is poor. Let's increase the test coverage. ref - subquery/scalar/test_delete_subquery.test - test/sql/subquery/scalar/test_update_subquery.test > Extend test coverage for SQL F861(Top-level in expression>) > - > > Key: IGNITE-21980 > URL: https://issues.apache.org/jira/browse/IGNITE-21980 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F861(Top-level in expression>) is poor. > Let's increase the test coverage. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21980) Extend test coverage for SQL F861(Top-level in )
Iurii Gerzhedovich created IGNITE-21980: --- Summary: Extend test coverage for SQL F861(Top-level in ) Key: IGNITE-21980 URL: https://issues.apache.org/jira/browse/IGNITE-21980 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F781(Self-referencing operations) is poor. Let's increase the test coverage. ref - subquery/scalar/test_delete_subquery.test - test/sql/subquery/scalar/test_update_subquery.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21979) Extend test coverage for SQL F781(Self-referencing operations)
[ https://issues.apache.org/jira/browse/IGNITE-21979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21979: Description: Test coverage for SQL F781(Self-referencing operations) is poor. Let's increase the test coverage. ref - subquery/scalar/test_delete_subquery.test - test/sql/subquery/scalar/test_update_subquery.test was: Test coverage for SQL F661(Simple tables) is poor. Let's increase the test coverage. > Extend test coverage for SQL F781(Self-referencing operations) > -- > > Key: IGNITE-21979 > URL: https://issues.apache.org/jira/browse/IGNITE-21979 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F781(Self-referencing operations) is poor. > Let's increase the test coverage. > > ref - subquery/scalar/test_delete_subquery.test > - test/sql/subquery/scalar/test_update_subquery.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21977) Extend test coverage for SQL F661(Simple tables)
[ https://issues.apache.org/jira/browse/IGNITE-21977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21977: Description: Test coverage for SQL F661(Simple tables) is poor. Let's increase the test coverage. was: Test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_complex_correlated_subquery.test > Extend test coverage for SQL F661(Simple tables) > > > Key: IGNITE-21977 > URL: https://issues.apache.org/jira/browse/IGNITE-21977 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F661(Simple tables) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21979) Extend test coverage for SQL F781(Self-referencing operations)
Iurii Gerzhedovich created IGNITE-21979: --- Summary: Extend test coverage for SQL F781(Self-referencing operations) Key: IGNITE-21979 URL: https://issues.apache.org/jira/browse/IGNITE-21979 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F661(Simple tables) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21978) Sql. Unexpected result from UNION with literals expression
Evgeny Stanilovsky created IGNITE-21978:
---
Summary: Sql. Unexpected result from UNION with literals expression
Key: IGNITE-21978
URL: https://issues.apache.org/jira/browse/IGNITE-21978
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 3.0.0-beta1
Reporter: Evgeny Stanilovsky
{noformat}
SELECT * from (SELECT 'hello' i union all SELECT 'h' i) t1 where i='h'
{noformat}
need to return 'h' but got nothing, appropriate calcite issue [1]
[1] https://issues.apache.org/jira/browse/CALCITE-6350
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21977) Extend test coverage for SQL F661(Simple tables)
Iurii Gerzhedovich created IGNITE-21977: --- Summary: Extend test coverage for SQL F661(Simple tables) Key: IGNITE-21977 URL: https://issues.apache.org/jira/browse/IGNITE-21977 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_complex_correlated_subquery.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21976) Sql. Amend TREE keyword to SORTED for CREATE INDEX syntax
[ https://issues.apache.org/jira/browse/IGNITE-21976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21976: Summary: Sql. Amend TREE keyword to SORTED for CREATE INDEX syntax (was: Amend TREE keyword to SORTED for CREATE INDEX syntax) > Sql. Amend TREE keyword to SORTED for CREATE INDEX syntax > - > > Key: IGNITE-21976 > URL: https://issues.apache.org/jira/browse/IGNITE-21976 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > After IGNITE-21353 we can use syntax to choose the type of PK index as SORTED > or HASH, but we still have different keywords for CREATE INDEX syntax where > we should use TREE or HASH types. Let's have the same keyword for the sorted > index. > So, required to rename TREE to SORTED for CREATE INDEX syntax -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21976) Amend TREE keyword to SORTED for CREATE INDEX syntax
Iurii Gerzhedovich created IGNITE-21976: --- Summary: Amend TREE keyword to SORTED for CREATE INDEX syntax Key: IGNITE-21976 URL: https://issues.apache.org/jira/browse/IGNITE-21976 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich After IGNITE-21353 we can use syntax to choose the type of PK index as SORTED or HASH, but we still have different keywords for CREATE INDEX syntax where we should use TREE or HASH types. Let's have the same keyword for the sorted index. So, required to rename TREE to SORTED for CREATE INDEX syntax -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21145) Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.*
[ https://issues.apache.org/jira/browse/IGNITE-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833899#comment-17833899 ] Julia Bakulina commented on IGNITE-21145: - [~av] could you please review? > Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.* > > > Key: IGNITE-21145 > URL: https://issues.apache.org/jira/browse/IGNITE-21145 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > Time Spent: 0.5h > Remaining Estimate: 0h > > Delete all classes from: > 1) org/apache/ignite/internal/processors/cache/tree/mvcc/data > * MvccCacheIdAwareDataInnerIO > * MvccCacheIdAwareDataLeafIO > * MvccDataInnerIO > * MvccDataLeafIO > * MvccDataRow > * MvccUpdateDataRow > * MvccUpdateResult > * ResultType > 2) org/apache/ignite/internal/processors/cache/tree/mvcc/search > * MvccDataPageClosure > * MvccFirstRowTreeClosure > * MvccLinkAwareSearchRow > * MvccMaxSearchRow > * MvccMinSearchRow > * MvccSearchRow > * MvccSnapshotSearchRow > * MvccTreeClosure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl. Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Description: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. (was: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f]) > catalog-dsl. Rename IndexType.TREE to SORTED > > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl. Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Summary: catalog-dsl. Rename IndexType.TREE to SORTED (was: catalog-dsl Rename IndexType.TREE to SORTED) > catalog-dsl. Rename IndexType.TREE to SORTED > > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Description: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] was: Rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] > Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Summary: catalog-dsl Rename IndexType.TREE to SORTED (was: Rename IndexType.TREE to SORTED) > catalog-dsl Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21145) Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.*
[
https://issues.apache.org/jira/browse/IGNITE-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833897#comment-17833897
]
Ignite TC Bot commented on IGNITE-21145:
{panel:title=Branch: [pull/11282/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11282/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7810476buildTypeId=IgniteTests24Java8_RunAll]
> Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.*
>
>
> Key: IGNITE-21145
> URL: https://issues.apache.org/jira/browse/IGNITE-21145
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Julia Bakulina
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Delete all classes from:
> 1) org/apache/ignite/internal/processors/cache/tree/mvcc/data
> * MvccCacheIdAwareDataInnerIO
> * MvccCacheIdAwareDataLeafIO
> * MvccDataInnerIO
> * MvccDataLeafIO
> * MvccDataRow
> * MvccUpdateDataRow
> * MvccUpdateResult
> * ResultType
> 2) org/apache/ignite/internal/processors/cache/tree/mvcc/search
> * MvccDataPageClosure
> * MvccFirstRowTreeClosure
> * MvccLinkAwareSearchRow
> * MvccMaxSearchRow
> * MvccMinSearchRow
> * MvccSearchRow
> * MvccSnapshotSearchRow
> * MvccTreeClosure
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21538) Rework component lifecycle mode to asynchronous
[
https://issues.apache.org/jira/browse/IGNITE-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov updated IGNITE-21538:
---
Description:
Current design for comp lifecycle has issues:
1. It was designed for synchronous components, but almost all components are
asynchronous.
This causes to appear ugly things like _inBusyLockAsync_ and inefficient code
like
_public @Nullable TxStateMeta stateMeta(UUID txId) \{ return
inBusyLock(busyLock, () -> txStateVolatileStorage.state(txId)); }_
2. Currently it's not possible to do truly graceful node shutdown, because IO
layer is disabled out-of-order, causing operation failures without a chance to
finish.
I suggest reworking comp lifecycle to async model:
1. Each component tracks it's inflight async ops (as list of async chains)
2. On start components are initialized using _CompletableFuture
startAsync()_ method from root to leafs of dependency tree
3. On shutdown
3.1 _CompletableFuturebeforeShutdown_ is called on comp from leafs to
root direction in dependency tree. This step waits for all active futures to
complete. Any new operation return a future completed with
_NodeStoppingException_
3.2 stop is called on comp from leafs to root direction in dependency tree.
This step destroys component resources, like pools, etc.
was:
Current design for comp lifecycle has issues:
1. It was designed for synchronous components, but almost all components are
asynchronous.
This causes to appear ugly things like _inBusyLockAsync_ and inefficient code
like
_public @Nullable TxStateMeta stateMeta(UUID txId) \{ return
inBusyLock(busyLock, () -> txStateVolatileStorage.state(txId)); }_
2. Currently it's not possible to do truly graceful node shutdown, because IO
layer is disabled out-of-order, causing operation failures without a chance to
finish.
I suggest to rework comp lifecycle to async model:
1. Each component tracks it's inflight async ops (as list of async chains)
2. On start components are initialized using _CompletableFuture
startAsync()_ method from root to leafs of dependency tree
3. On shutdown
3.1 _CompletableFuturebeforeShutdown_ is called on comp from leafs to
root direction in dependency tree. This step waits for all active futures to
complete. Any new operation return a future completed with
_NodeStoppingException_
3.2 stop is called on comp from leafs to root direction in dependency tree.
This step destroys component resources, like pools, etc.
> Rework component lifecycle mode to asynchronous
> ---
>
> Key: IGNITE-21538
> URL: https://issues.apache.org/jira/browse/IGNITE-21538
> Project: Ignite
> Issue Type: Task
>Affects Versions: 3.0.0-beta2
>Reporter: Alexey Scherbakov
>Assignee: Kirill Sizov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
>
> Current design for comp lifecycle has issues:
> 1. It was designed for synchronous components, but almost all components are
> asynchronous.
> This causes to appear ugly things like _inBusyLockAsync_ and inefficient code
> like
> _public @Nullable TxStateMeta stateMeta(UUID txId) \{ return
> inBusyLock(busyLock, () -> txStateVolatileStorage.state(txId)); }_
> 2. Currently it's not possible to do truly graceful node shutdown, because IO
> layer is disabled out-of-order, causing operation failures without a chance
> to finish.
> I suggest reworking comp lifecycle to async model:
> 1. Each component tracks it's inflight async ops (as list of async chains)
> 2. On start components are initialized using _CompletableFuture
> startAsync()_ method from root to leafs of dependency tree
> 3. On shutdown
> 3.1 _CompletableFuturebeforeShutdown_ is called on comp from leafs to
> root direction in dependency tree. This step waits for all active futures to
> complete. Any new operation return a future completed with
> _NodeStoppingException_
> 3.2 stop is called on comp from leafs to root direction in dependency tree.
> This step destroys component resources, like pools, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21975) Extend test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator)
[ https://issues.apache.org/jira/browse/IGNITE-21975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21975: Description: Test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/scalar/test_complex_correlated_subquery.test was: Test coverage for SQL F221(Explicit defaults) is poor. Let's increase the test coverage. > Extend test coverage for SQL F302-01(INTERSECT table operator. INTERSECT > DISTINCT table operator) > - > > Key: IGNITE-21975 > URL: https://issues.apache.org/jira/browse/IGNITE-21975 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT > table operator) is poor. > Let's increase the test coverage. > ref - test/sql/subquery/scalar/test_complex_correlated_subquery.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21975) Extend test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator)
Iurii Gerzhedovich created IGNITE-21975: --- Summary: Extend test coverage for SQL F302-01(INTERSECT table operator. INTERSECT DISTINCT table operator) Key: IGNITE-21975 URL: https://issues.apache.org/jira/browse/IGNITE-21975 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F221(Explicit defaults) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21974) CLONE - Extend test coverage for SQL F201(CAST function)
Iurii Gerzhedovich created IGNITE-21974: --- Summary: CLONE - Extend test coverage for SQL F201(CAST function) Key: IGNITE-21974 URL: https://issues.apache.org/jira/browse/IGNITE-21974 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F201(CAST function) is poor. Let's increase the test coverage. ref - test/sql/cast/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21974) Extend test coverage for SQL F221(Explicit defaults)
[ https://issues.apache.org/jira/browse/IGNITE-21974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21974: Description: Test coverage for SQL F221(Explicit defaults) is poor. Let's increase the test coverage. was: Test coverage for SQL F201(CAST function) is poor. Let's increase the test coverage. ref - test/sql/cast/ > Extend test coverage for SQL F221(Explicit defaults) > > > Key: IGNITE-21974 > URL: https://issues.apache.org/jira/browse/IGNITE-21974 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F221(Explicit defaults) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21974) Extend test coverage for SQL F221(Explicit defaults)
[ https://issues.apache.org/jira/browse/IGNITE-21974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21974: Summary: Extend test coverage for SQL F221(Explicit defaults) (was: CLONE - Extend test coverage for SQL F201(CAST function)) > Extend test coverage for SQL F221(Explicit defaults) > > > Key: IGNITE-21974 > URL: https://issues.apache.org/jira/browse/IGNITE-21974 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F201(CAST function) is poor. > Let's increase the test coverage. > > ref - test/sql/cast/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21973) Extend test coverage for SQL F201(CAST function)
[ https://issues.apache.org/jira/browse/IGNITE-21973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21973: Description: Test coverage for SQL F201(CAST function) is poor. Let's increase the test coverage. ref - test/sql/cast/ was: Test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest > Extend test coverage for SQL F201(CAST function) > > > Key: IGNITE-21973 > URL: https://issues.apache.org/jira/browse/IGNITE-21973 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F201(CAST function) is poor. > Let's increase the test coverage. > > ref - test/sql/cast/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21973) Extend test coverage for SQL F201(CAST function)
Iurii Gerzhedovich created IGNITE-21973: --- Summary: Extend test coverage for SQL F201(CAST function) Key: IGNITE-21973 URL: https://issues.apache.org/jira/browse/IGNITE-21973 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21972) Extend test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP)
[ https://issues.apache.org/jira/browse/IGNITE-21972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21972: Description: Test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest was: Test coverage for SQL F051-07(Basic date and time. LOCALTIME) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest > Extend test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) > - > > Key: IGNITE-21972 > URL: https://issues.apache.org/jira/browse/IGNITE-21972 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) is poor. > Let's increase the test coverage. > > ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21971) Extend test coverage for SQL F051-07(Basic date and time. LOCALTIME)
[ https://issues.apache.org/jira/browse/IGNITE-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21971: Description: Test coverage for SQL F051-07(Basic date and time. LOCALTIME) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest was: Test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest > Extend test coverage for SQL F051-07(Basic date and time. LOCALTIME) > > > Key: IGNITE-21971 > URL: https://issues.apache.org/jira/browse/IGNITE-21971 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F051-07(Basic date and time. LOCALTIME) is poor. > Let's increase the test coverage. > > ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21972) Extend test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP)
Iurii Gerzhedovich created IGNITE-21972: --- Summary: Extend test coverage for SQL F051-08(Basic date and time. LOCALTIMESTAMP) Key: IGNITE-21972 URL: https://issues.apache.org/jira/browse/IGNITE-21972 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F051-07(Basic date and time. LOCALTIME) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21971) Extend test coverage for SQL F051-07(Basic date and time. LOCALTIME)
Iurii Gerzhedovich created IGNITE-21971: --- Summary: Extend test coverage for SQL F051-07(Basic date and time. LOCALTIME) Key: IGNITE-21971 URL: https://issues.apache.org/jira/browse/IGNITE-21971 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21970) Extend test coverage for SQL F051-06(Basic date and time. CURRENT_DATE)
[ https://issues.apache.org/jira/browse/IGNITE-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21970: Description: Test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) is poor. Let's increase the test coverage. ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest was: Test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause) is poor. Let's increase the test coverage. > Extend test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) > --- > > Key: IGNITE-21970 > URL: https://issues.apache.org/jira/browse/IGNITE-21970 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) is poor. > Let's increase the test coverage. > > ref - org.apache.ignite.internal.sql.engine.ItFunctionsTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21970) Extend test coverage for SQL F051-06(Basic date and time. CURRENT_DATE)
Iurii Gerzhedovich created IGNITE-21970: --- Summary: Extend test coverage for SQL F051-06(Basic date and time. CURRENT_DATE) Key: IGNITE-21970 URL: https://issues.apache.org/jira/browse/IGNITE-21970 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21969) Extend test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause)
[ https://issues.apache.org/jira/browse/IGNITE-21969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21969: Description: Test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause) is poor. Let's increase the test coverage. was: Test coverage for SQL E141-07(Basic integrity constraints. Column defaults) is poor. Let's increase the test coverage. > Extend test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE > statement: ADD COLUMN clause) > - > > Key: IGNITE-21969 > URL: https://issues.apache.org/jira/browse/IGNITE-21969 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE > statement: ADD COLUMN clause) is poor. > Let's increase the test coverage. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21969) Extend test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause)
Iurii Gerzhedovich created IGNITE-21969: --- Summary: Extend test coverage for SQL F031-04(Basic schema manipulation. ALTER TABLE statement: ADD COLUMN clause) Key: IGNITE-21969 URL: https://issues.apache.org/jira/browse/IGNITE-21969 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E141-07(Basic integrity constraints. Column defaults) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21968) Extend test coverage for SQL E141-07(Basic integrity constraints. Column defaults)
[ https://issues.apache.org/jira/browse/IGNITE-21968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21968: Description: Test coverage for SQL E141-07(Basic integrity constraints. Column defaults) is poor. Let's increase the test coverage. was: Test coverage for SQL E091-06(Set functions. ALL quantifier) is poor. Let's increase the test coverage. ref - modules/runner/src/integrationTest/sql/sqlite/aggregates/agg4.test_slow > Extend test coverage for SQL E141-07(Basic integrity constraints. Column > defaults) > -- > > Key: IGNITE-21968 > URL: https://issues.apache.org/jira/browse/IGNITE-21968 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E141-07(Basic integrity constraints. Column defaults) > is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21968) Extend test coverage for SQL E141-07(Basic integrity constraints. Column defaults)
Iurii Gerzhedovich created IGNITE-21968: --- Summary: Extend test coverage for SQL E141-07(Basic integrity constraints. Column defaults) Key: IGNITE-21968 URL: https://issues.apache.org/jira/browse/IGNITE-21968 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E091-06(Set functions. ALL quantifier) is poor. Let's increase the test coverage. ref - modules/runner/src/integrationTest/sql/sqlite/aggregates/agg4.test_slow -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21967) Extend test coverage for SQL E091-06(Set functions. ALL quantifier)
[ https://issues.apache.org/jira/browse/IGNITE-21967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21967: Description: Test coverage for SQL E091-06(Set functions. ALL quantifier) is poor. Let's increase the test coverage. ref - modules/runner/src/integrationTest/sql/sqlite/aggregates/agg4.test_slow was: Test coverage for SQL E091-01(Set functions. AVG) is poor. Let's increase the test coverage. ref - test/sql/aggregate/aggregates/test_avg.test > Extend test coverage for SQL E091-06(Set functions. ALL quantifier) > --- > > Key: IGNITE-21967 > URL: https://issues.apache.org/jira/browse/IGNITE-21967 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E091-06(Set functions. ALL quantifier) is poor. > Let's increase the test coverage. > > ref - modules/runner/src/integrationTest/sql/sqlite/aggregates/agg4.test_slow -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21967) Extend test coverage for SQL E091-06(Set functions. ALL quantifier)
Iurii Gerzhedovich created IGNITE-21967: --- Summary: Extend test coverage for SQL E091-06(Set functions. ALL quantifier) Key: IGNITE-21967 URL: https://issues.apache.org/jira/browse/IGNITE-21967 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E091-01(Set functions. AVG) is poor. Let's increase the test coverage. ref - test/sql/aggregate/aggregates/test_avg.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21966) Extend test coverage for SQL E091-01(Set functions. AVG)
Iurii Gerzhedovich created IGNITE-21966: --- Summary: Extend test coverage for SQL E091-01(Set functions. AVG) Key: IGNITE-21966 URL: https://issues.apache.org/jira/browse/IGNITE-21966 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/table/test_subquery_union.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21966) Extend test coverage for SQL E091-01(Set functions. AVG)
[ https://issues.apache.org/jira/browse/IGNITE-21966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21966: Description: Test coverage for SQL E091-01(Set functions. AVG) is poor. Let's increase the test coverage. ref - test/sql/aggregate/aggregates/test_avg.test was: Test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/table/test_subquery_union.test > Extend test coverage for SQL E091-01(Set functions. AVG) > > > Key: IGNITE-21966 > URL: https://issues.apache.org/jira/browse/IGNITE-21966 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E091-01(Set functions. AVG) is poor. > Let's increase the test coverage. > > ref - test/sql/aggregate/aggregates/test_avg.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21965) Extend test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator)
[ https://issues.apache.org/jira/browse/IGNITE-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21965: Description: Test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator) is poor. Let's increase the test coverage. ref - test/sql/subquery/table/test_subquery_union.test was: Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. Let's increase the test coverage. > Extend test coverage for SQL E071-02(Basic query expressions. UNION ALL table > operator) > --- > > Key: IGNITE-21965 > URL: https://issues.apache.org/jira/browse/IGNITE-21965 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E071-02(Basic query expressions. UNION ALL table > operator) is poor. > Let's increase the test coverage. > > ref - test/sql/subquery/table/test_subquery_union.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21965) Extend test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator)
Iurii Gerzhedovich created IGNITE-21965: --- Summary: Extend test coverage for SQL E071-02(Basic query expressions. UNION ALL table operator) Key: IGNITE-21965 URL: https://issues.apache.org/jira/browse/IGNITE-21965 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19274) Sql. Jdbc client. Support TIMESTAMP WITH LOCAL TIME ZONE type
[
https://issues.apache.org/jira/browse/IGNITE-19274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-19274:
--
Ignite Flags: Docs Required
> Sql. Jdbc client. Support TIMESTAMP WITH LOCAL TIME ZONE type
> --
>
> Key: IGNITE-19274
> URL: https://issues.apache.org/jira/browse/IGNITE-19274
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The {{TIMESTAMP WITH LOCAL TIME ZONE}} data type is a variant of
> {{TIMESTAMP}} that includes a time zone offset in its value. Data stored in
> the database is normalized to the database time zone (UTC) and time zone
> offset is not stored as part of the column data. When the data is retrieved,
> it to be returned in the user's local session time zone.
> i.e:
> {noformat}
> CREATE TABLE timestamp(ts TIMESTAMP, t_tz TIMESTAMP WITH LOCAL TIME ZONE);
> SET TIME ZONE 'tz1';
> INSERT INTO timestamp VALUES ('2011-01-01 01:01:01', TIMESTAMP WITH LOCAL
> TIME ZONE '2011-01-01 01:01:01');
> SET TIME ZONE 'tz2';
> INSERT INTO timestamp VALUES ('2011-01-01 01:01:01', TIMESTAMP WITH LOCAL
> TIME ZONE '2011-01-01 01:01:01');
> ...
> select * from timestamp;{noformat}
> returned rows need to be different in case of different tz1 and tz2 offsets
> but they are equals for now. Also returned representation need to be present
> in user session time zone.
> h5. Update from 26.02.2024:
> Definition of done for this task:
> * Client time zone is passed to server (check other database implementations
> to decide how and when to pass it).
> * Data of type "TIMESTAMP With LOCAL TIME ZONE" can be written/read correctly
> using the dynamic parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21964) Extend test coverage for SQL E031-1(Identifiers. Delimited identifiers)
[ https://issues.apache.org/jira/browse/IGNITE-21964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21964: Description: Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. Let's increase the test coverage. was: Test coverage for SQL E061-07(Basic predicates and search conditions. Quantified comparison predicate) is poor. Let's increase the test coverage. ref - modules/runner/src/integrationTest/sql/subquery/scalar/test_correlated_aggregate_subquery.test > Extend test coverage for SQL E031-1(Identifiers. Delimited identifiers) > --- > > Key: IGNITE-21964 > URL: https://issues.apache.org/jira/browse/IGNITE-21964 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21964) Extend test coverage for SQL E031-1(Identifiers. Delimited identifiers)
Iurii Gerzhedovich created IGNITE-21964: --- Summary: Extend test coverage for SQL E031-1(Identifiers. Delimited identifiers) Key: IGNITE-21964 URL: https://issues.apache.org/jira/browse/IGNITE-21964 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich Test coverage for SQL E061-07(Basic predicates and search conditions. Quantified comparison predicate) is poor. Let's increase the test coverage. ref - modules/runner/src/integrationTest/sql/subquery/scalar/test_correlated_aggregate_subquery.test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21721) Sql. Adjust cost estimation for index scan
[ https://issues.apache.org/jira/browse/IGNITE-21721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21721: -- Description: Scan over an index if significantly slower than scan over a table. In some cases (for example, TPC-H q1 on scaleFactor=0.1) it's faster to read an entire table and do sorting in memory rather than scan the index. Let's adjust cost function to reflect the real complexity of index scan. was: Scan over an index if significantly slower than scan over a table. In some cases (for example, TPC-H q4 on scaleFactor=0.1) it's faster to read an entire table and do sorting in memory rather than scan the index. Let's adjust cost function to reflect the real complexity of index scan. > Sql. Adjust cost estimation for index scan > -- > > Key: IGNITE-21721 > URL: https://issues.apache.org/jira/browse/IGNITE-21721 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Scan over an index if significantly slower than scan over a table. In some > cases (for example, TPC-H q1 on scaleFactor=0.1) it's faster to read an > entire table and do sorting in memory rather than scan the index. > Let's adjust cost function to reflect the real complexity of index scan. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21963) flaky KvMarshallerTest#basicTypes
[
https://issues.apache.org/jira/browse/IGNITE-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-21963:
Description:
The test
org.apache.ignite.internal.schema.marshaller.KvMarshallerTest#basicTypes is
flaky on TC
([link|https://ci.ignite.apache.org/test/8717516430421609050?currentProjectId=ApacheIgnite3xGradle_Test_RunUnitTests_virtual=true])
Locally it is also reproducible, just run it until failure mode.
{code:java}
org.apache.ignite.internal.marshaller.MarshallerException: IGN-CMN-65535
TraceId:40e8232a-643d-4753-9916-9b900e6e21fa Offset entry overflow in binary
tuple builder at
org.apache.ignite.internal.schema.marshaller.MarshallerForSchema_1800.marshal(Unknown
Source)
at
org.apache.ignite.internal.schema.marshaller.KvMarshallerTest.checkBasicType(KvMarshallerTest.java:731)
at
org.apache.ignite.internal.schema.marshaller.KvMarshallerTest.lambda$basicTypes$8(KvMarshallerTest.java:162)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
at
java.base/java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:735)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at
java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.forEachOrdered(ReferencePipeline.java:601)
at java.base/java.util.Optional.ifPresent(Optional.java:178)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.IllegalStateException: Offset entry overflow in binary
tuple builder
at
org.apache.ignite.internal.binarytuple.BinaryTupleBuilder.buildInternal(BinaryTupleBuilder.java:653)
at
org.apache.ignite.internal.binarytuple.BinaryTupleBuilder.build(BinaryTupleBuilder.java:640)
at
org.apache.ignite.internal.schema.row.RowAssembler.build(RowAssembler.java:598)
{code}
was:
The test
org.apache.ignite.internal.schema.marshaller.KvMarshallerTest#basicTypes is
flaky on TC
([link|https://ci.ignite.apache.org/test/8717516430421609050?currentProjectId=ApacheIgnite3xGradle_Test_RunUnitTests_virtual=true])
Locally it is also reproducible, just run it until failure mode.
> flaky KvMarshallerTest#basicTypes
> -
>
> Key: IGNITE-21963
> URL: https://issues.apache.org/jira/browse/IGNITE-21963
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> The test
> org.apache.ignite.internal.schema.marshaller.KvMarshallerTest#basicTypes is
> flaky on TC
> ([link|https://ci.ignite.apache.org/test/8717516430421609050?currentProjectId=ApacheIgnite3xGradle_Test_RunUnitTests_virtual=true])
>
> Locally it is also reproducible, just run it until failure mode.
> {code:java}
> org.apache.ignite.internal.marshaller.MarshallerException: IGN-CMN-65535
> TraceId:40e8232a-643d-4753-9916-9b900e6e21fa Offset entry overflow in binary
> tuple builder at
> org.apache.ignite.internal.schema.marshaller.MarshallerForSchema_1800.marshal(Unknown
> Source)
> at
> org.apache.ignite.internal.schema.marshaller.KvMarshallerTest.checkBasicType(KvMarshallerTest.java:731)
> at
> org.apache.ignite.internal.schema.marshaller.KvMarshallerTest.lambda$basicTypes$8(KvMarshallerTest.java:162)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
> at
> java.base/java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:735)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
> at
>
[jira] [Created] (IGNITE-21963) flaky KvMarshallerTest#basicTypes
Iurii Gerzhedovich created IGNITE-21963: --- Summary: flaky KvMarshallerTest#basicTypes Key: IGNITE-21963 URL: https://issues.apache.org/jira/browse/IGNITE-21963 Project: Ignite Issue Type: Improvement Reporter: Iurii Gerzhedovich The test org.apache.ignite.internal.schema.marshaller.KvMarshallerTest#basicTypes is flaky on TC ([link|https://ci.ignite.apache.org/test/8717516430421609050?currentProjectId=ApacheIgnite3xGradle_Test_RunUnitTests_virtual=true]) Locally it is also reproducible, just run it until failure mode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21962) ignite-client-handler tests fail due to hardcoded handshake response size
[ https://issues.apache.org/jira/browse/IGNITE-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21962: Description: The following tests fail if you change *IgniteProductVersion.CURRENT_VERSION* so that the string length is different, because handshake response size changes: * *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* was: * *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* > ignite-client-handler tests fail due to hardcoded handshake response size > - > > Key: IGNITE-21962 > URL: https://issues.apache.org/jira/browse/IGNITE-21962 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > The following tests fail if you change *IgniteProductVersion.CURRENT_VERSION* > so that the string length is different, because handshake response size > changes: > > * > *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21962) ignite-client-handler tests fail due to hardcoded handshake response size
[ https://issues.apache.org/jira/browse/IGNITE-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21962: Description: * *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* * *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* > ignite-client-handler tests fail due to hardcoded handshake response size > - > > Key: IGNITE-21962 > URL: https://issues.apache.org/jira/browse/IGNITE-21962 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * > *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21962) ignite-client-handler tests fail due to hardcoded handshake response size
Pavel Tupitsyn created IGNITE-21962: --- Summary: ignite-client-handler tests fail due to hardcoded handshake response size Key: IGNITE-21962 URL: https://issues.apache.org/jira/browse/IGNITE-21962 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20516: -- Assignee: Mikhail Pochatkin > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21427) Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-21427: -- Assignee: Vadim Kolodin > Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > Rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21921) Cover SQL E071-1 (Basic query expressions, UNION DISTINCT table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky reassigned IGNITE-21921: --- Assignee: Evgeny Stanilovsky > Cover SQL E071-1 (Basic query expressions, UNION DISTINCT table operator) > feature by tests > -- > > Key: IGNITE-21921 > URL: https://issues.apache.org/jira/browse/IGNITE-21921 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E071-1 (Basic query expressions, UNION > DISTINCT table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21961) Don't remove entries one-by-one for in-memory node on shutdown
Aleksey Plekhanov created IGNITE-21961: -- Summary: Don't remove entries one-by-one for in-memory node on shutdown Key: IGNITE-21961 URL: https://issues.apache.org/jira/browse/IGNITE-21961 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Currently, for in-memory node we remove each entry one-by-one on cluster deactivation or on node shutdown. If there are a lot of entries in cache it can take a long time. But it's a redundant action, since all page memory will be released after deactivation/shutdown. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21909) RocksDbMvTableStorageTest#testDestroyIndex is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833832#comment-17833832
]
Roman Puchkovskiy commented on IGNITE-21909:
The patch looks good to me
> RocksDbMvTableStorageTest#testDestroyIndex is flaky
> ---
>
> Key: IGNITE-21909
> URL: https://issues.apache.org/jira/browse/IGNITE-21909
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There's a race between destroying and getting an index storage in
> {{RocksDbMvTableStorage}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
