[jira] [Updated] (IGNITE-21890) AbstractSortedIndexStorageTest#testScan is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21890:
-
Description: Looks like {{BinaryTupleComparator}} handles decimal values
incorrectly, this test fails sometimes if a {{DECIMAL}} column is present in
the index descriptor.
> AbstractSortedIndexStorageTest#testScan is flaky
>
>
> Key: IGNITE-21890
> URL: https://issues.apache.org/jira/browse/IGNITE-21890
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looks like {{BinaryTupleComparator}} handles decimal values incorrectly, this
> test fails sometimes if a {{DECIMAL}} column is present in the index
> descriptor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21796) Update grpc in opencensus module
[ https://issues.apache.org/jira/browse/IGNITE-21796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-21796: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update grpc in opencensus module > > > Key: IGNITE-21796 > URL: https://issues.apache.org/jira/browse/IGNITE-21796 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Nikolaev >Assignee: Andrei Nadyktov >Priority: Major > Labels: ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Update grpc-context 1.61.0 to 1.62.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21223) Add xml example WAL Records Compression
[ https://issues.apache.org/jira/browse/IGNITE-21223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky resolved IGNITE-21223. -- Resolution: Fixed Thank you for your contribution, merged > Add xml example WAL Records Compression > > > Key: IGNITE-21223 > URL: https://issues.apache.org/jira/browse/IGNITE-21223 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Andrei Nadyktov >Priority: Major > Labels: ise, newbee > Fix For: 2.17 > > Attachments: walcompress.png > > Time Spent: 20m > Remaining Estimate: 0h > > Add xml example WAL Records Compression > [https://ignite.apache.org/docs/latest/persistence/native-persistence#wal-records-compression] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21223) Add xml example WAL Records Compression
[ https://issues.apache.org/jira/browse/IGNITE-21223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-21223: - Ignite Flags: (was: Docs Required,Release Notes Required) > Add xml example WAL Records Compression > > > Key: IGNITE-21223 > URL: https://issues.apache.org/jira/browse/IGNITE-21223 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Andrei Nadyktov >Priority: Major > Labels: ise, newbee > Fix For: 2.17 > > Attachments: walcompress.png > > Time Spent: 20m > Remaining Estimate: 0h > > Add xml example WAL Records Compression > [https://ignite.apache.org/docs/latest/persistence/native-persistence#wal-records-compression] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IGNITE-21889) Remove TxState
[ https://issues.apache.org/jira/browse/IGNITE-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina reopened IGNITE-21889: - > Remove TxState > -- > > Key: IGNITE-21889 > URL: https://issues.apache.org/jira/browse/IGNITE-21889 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21499) Removal of MvccSnapshot
[ https://issues.apache.org/jira/browse/IGNITE-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina reassigned IGNITE-21499: --- Assignee: Julia Bakulina > Removal of MvccSnapshot > --- > > Key: IGNITE-21499 > URL: https://issues.apache.org/jira/browse/IGNITE-21499 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21889) Remove TxState
[ https://issues.apache.org/jira/browse/IGNITE-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina resolved IGNITE-21889. - Resolution: Duplicate > Remove TxState > -- > > Key: IGNITE-21889 > URL: https://issues.apache.org/jira/browse/IGNITE-21889 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21345) TxState removal
[ https://issues.apache.org/jira/browse/IGNITE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina reassigned IGNITE-21345: --- Assignee: Julia Bakulina > TxState removal > --- > > Key: IGNITE-21345 > URL: https://issues.apache.org/jira/browse/IGNITE-21345 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > > Remove o.a.i.internal.processors.cache.mvcc.txlog.TxState (as a continuation > of the IGNITE-21130) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov reassigned IGNITE-21891: - Assignee: Maksim Zhuravkov > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Maksim Zhuravkov >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > * *deleteAll/removeAll* methods return key-only rows > * *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21876) Prevent thread hijacking via IgniteCompute
[ https://issues.apache.org/jira/browse/IGNITE-21876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21876: --- Reviewer: (was: Kirill Tkalenko) > Prevent thread hijacking via IgniteCompute > -- > > Key: IGNITE-21876 > URL: https://issues.apache.org/jira/browse/IGNITE-21876 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, threading > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Methods of IgniteCompute that return CompletableFutures must wrap their > return value with PublicApiThreading#preventThreadHijack(). Also, tests need > to be created (similar to ItKvRecordApiThreadingTest). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21876) Prevent thread hijacking via IgniteCompute
[ https://issues.apache.org/jira/browse/IGNITE-21876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832270#comment-17832270 ] Roman Puchkovskiy commented on IGNITE-21876: Oops, wrong mention > Prevent thread hijacking via IgniteCompute > -- > > Key: IGNITE-21876 > URL: https://issues.apache.org/jira/browse/IGNITE-21876 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, threading > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Methods of IgniteCompute that return CompletableFutures must wrap their > return value with PublicApiThreading#preventThreadHijack(). Also, tests need > to be created (similar to ItKvRecordApiThreadingTest). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21892:
--
Description:
This test is flaky. Build error:
{code}
java.lang.AssertionError: There are replicas alive [replicas=[group_1]]
at
org.apache.ignite.internal.replicator.ReplicaManager.stop(ReplicaManager.java:658)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.lambda$beforeTest$3(ItPlacementDriverReplicaSideTest.java:200)
at
org.apache.ignite.internal.util.IgniteUtils.lambda$closeAll$0(IgniteUtils.java:559)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
at
java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
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.forEach(ReferencePipeline.java:497)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:557)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:580)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.afterTest(ItPlacementDriverReplicaSideTest.java:214)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
{code}
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware
I was not able to reproduce the same error locally, I got an error on the
following line instead:
{code}
assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() ==
placementDriverNodeNames.size(), 10_000));
{code}
was:
This test is flaky. Build error:
{code}
java.lang.AssertionError: There are replicas alive [replicas=[group_1]]
at
org.apache.ignite.internal.replicator.ReplicaManager.stop(ReplicaManager.java:658)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.lambda$beforeTest$3(ItPlacementDriverReplicaSideTest.java:200)
at
org.apache.ignite.internal.util.IgniteUtils.lambda$closeAll$0(IgniteUtils.java:559)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
at
java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
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.forEach(ReferencePipeline.java:497)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:557)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:580)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.afterTest(ItPlacementDriverReplicaSideTest.java:214)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
{code}
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware
I was not able to reproduce the same error locally, I got this an error on the
following line instead:
{code}
assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() ==
placementDriverNodeNames.size(), 10_000));
{code}
> ItPlacementDriverReplicaSideTest
> testNotificationToPlacementDriverAboutChangeLeader is flaky
>
[jira] [Updated] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21892:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> ItPlacementDriverReplicaSideTest
> testNotificationToPlacementDriverAboutChangeLeader is flaky
>
>
> Key: IGNITE-21892
> URL: https://issues.apache.org/jira/browse/IGNITE-21892
> Project: Ignite
> Issue Type: Bug
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: ignite-3
>
> This test is flaky. Build error:
> {code}
> java.lang.AssertionError: There are replicas alive [replicas=[group_1]]
> at
> org.apache.ignite.internal.replicator.ReplicaManager.stop(ReplicaManager.java:658)
> at
> org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.lambda$beforeTest$3(ItPlacementDriverReplicaSideTest.java:200)
> at
> org.apache.ignite.internal.util.IgniteUtils.lambda$closeAll$0(IgniteUtils.java:559)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> 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.forEach(ReferencePipeline.java:497)
> at
> org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:557)
> at
> org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:580)
> at
> org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.afterTest(ItPlacementDriverReplicaSideTest.java:214)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> {code}
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware
> I was not able to reproduce the same error locally, I got this an error on
> the following line instead:
> {code}
> assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() ==
> placementDriverNodeNames.size(), 10_000));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21892:
--
Description:
This test is flaky. Build error:
{code}
java.lang.AssertionError: There are replicas alive [replicas=[group_1]]
at
org.apache.ignite.internal.replicator.ReplicaManager.stop(ReplicaManager.java:658)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.lambda$beforeTest$3(ItPlacementDriverReplicaSideTest.java:200)
at
org.apache.ignite.internal.util.IgniteUtils.lambda$closeAll$0(IgniteUtils.java:559)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
at
java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
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.forEach(ReferencePipeline.java:497)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:557)
at
org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:580)
at
org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.afterTest(ItPlacementDriverReplicaSideTest.java:214)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
{code}
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware
I was not able to reproduce the same error locally, I got this an error on the
following line instead:
{code}
assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() ==
placementDriverNodeNames.size(), 10_000));
{code}
was:
This test is flaky. I was able to reproduce the same error locally but with
another error:
assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() ==
placementDriverNodeNames.size(), 10_000));
Build error
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware
> ItPlacementDriverReplicaSideTest
> testNotificationToPlacementDriverAboutChangeLeader is flaky
>
>
> Key: IGNITE-21892
> URL: https://issues.apache.org/jira/browse/IGNITE-21892
> Project: Ignite
> Issue Type: Bug
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: ignite-3
>
> This test is flaky. Build error:
> {code}
> java.lang.AssertionError: There are replicas alive [replicas=[group_1]]
> at
> org.apache.ignite.internal.replicator.ReplicaManager.stop(ReplicaManager.java:658)
> at
> org.apache.ignite.internal.replicator.ItPlacementDriverReplicaSideTest.lambda$beforeTest$3(ItPlacementDriverReplicaSideTest.java:200)
> at
> org.apache.ignite.internal.util.IgniteUtils.lambda$closeAll$0(IgniteUtils.java:559)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> 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.forEach(ReferencePipeline.java:497)
> at
> org.apache.ignite.internal.util.IgniteUtils.closeAll(IgniteUtils.java:557)
> at
>
[jira] [Created] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
Maksim Zhuravkov created IGNITE-21892: - Summary: ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky Key: IGNITE-21892 URL: https://issues.apache.org/jira/browse/IGNITE-21892 Project: Ignite Issue Type: Bug Reporter: Maksim Zhuravkov This test is flaky. I was able to reproduce the same error locally but with another error: assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() == placementDriverNodeNames.size(), 10_000)); Build error https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
[ https://issues.apache.org/jira/browse/IGNITE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21892: -- Labels: ignite-3 (was: ) > ItPlacementDriverReplicaSideTest > testNotificationToPlacementDriverAboutChangeLeader is flaky > > > Key: IGNITE-21892 > URL: https://issues.apache.org/jira/browse/IGNITE-21892 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > This test is flaky. I was able to reproduce the same error locally but with > another error: > assertTrue(waitForCondition(() -> nodesToReceivedDeclineMsg.size() == > placementDriverNodeNames.size(), 10_000)); > Build error > https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleReplicator/7987165?expandBuildDeploymentsSection=false=false=true=false=true=true=7987165_489_86.470.489=debug=flowAware -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891 ] Pavel Tupitsyn deleted comment on IGNITE-21891: - was (Author: ptupitsyn): [~isapego] please review. > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > * *deleteAll/removeAll* methods return key-only rows > * *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-21891: --- Assignee: Pavel Tupitsyn > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > * *deleteAll/removeAll* methods return key-only rows > * *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-21891: --- Assignee: (was: Pavel Tupitsyn) > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > * *deleteAll/removeAll* methods return key-only rows > * *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21877) Wrong column deserialization order in ClientKeyValueView
[ https://issues.apache.org/jira/browse/IGNITE-21877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832236#comment-17832236 ] Pavel Tupitsyn commented on IGNITE-21877: - Merged to main: 35ef7213b0dc05ba7d32f53eaf918800ecbdfae5 > Wrong column deserialization order in ClientKeyValueView > > > Key: IGNITE-21877 > URL: https://issues.apache.org/jira/browse/IGNITE-21877 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > IGNITE-21768 fix was incomplete - some places still use old logic: > * *readGetAllResponse* > * *queryMapper* > Make sure to add tests for all operations in all views to > *ItCustomKeyColumnOrderClientTest* . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21877) Wrong column deserialization order in ClientKeyValueView
[ https://issues.apache.org/jira/browse/IGNITE-21877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832233#comment-17832233 ] Igor Sapego commented on IGNITE-21877: -- Looks good to me. > Wrong column deserialization order in ClientKeyValueView > > > Key: IGNITE-21877 > URL: https://issues.apache.org/jira/browse/IGNITE-21877 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-21768 fix was incomplete - some places still use old logic: > * *readGetAllResponse* > * *queryMapper* > Make sure to add tests for all operations in all views to > *ItCustomKeyColumnOrderClientTest* . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-15622) Calcite. TIME and TIMESTAMP types are trim milliseconds.
[
https://issues.apache.org/jira/browse/IGNITE-15622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-15622:
-
Assignee: Pavel Pereslegin
> Calcite. TIME and TIMESTAMP types are trim milliseconds.
>
>
> Key: IGNITE-15622
> URL: https://issues.apache.org/jira/browse/IGNITE-15622
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
>
> for example ^
> {noformat}
> query I
> SELECT '1969-01-01 01:03:20.45432'::TIMESTAMP::VARCHAR
>
> 1969-01-01 01:03:20.45432
> expected=1969-01-01 01:03:20.45432, actual=1969-01-01 01:03:20
> {noformat}
> {noformat}
> query I
> SELECT '14:42:04.35'::TIME::VARCHAR
>
> 14:42:04.35
> expected=14:42:04.35, actual=14:42:04
> {noformat}
> {noformat}
> /sql/types/timestamp/bc_timestamp.test[_ignore]
> /sql/types/time/time_parsing.test
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15619) Calcite. Fix numerous errors with DATE TIME types tests.
[
https://issues.apache.org/jira/browse/IGNITE-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832201#comment-17832201
]
Pavel Pereslegin edited comment on IGNITE-15619 at 3/29/24 3:13 PM:
The described example is related to IGNITE-15123 issue.
I think this issue mostly relates to different date formats and negative form.
For example:
{code:sql}
SELECT '-1000-01-01'::DATE::VARCHAR = '1001-01-01 (BC)'
SELECT '3-01-01'::DATE::VARCHAR = '3-01-01'
{code}
As I understand such dates are not supported by Calcite currently
([CALCITE-5629|https://issues.apache.org/jira/browse/CALCITE-5629]).
{code:sql}
SELECT '1992/09/20'::DATE::VARCHAR = '1992-09-20'
{code}
Such format is not supported.
was (Author: xtern):
The described example is related to IGNITE-15123 issue.
I think this issue mostly relates to different date formats and negative form.
For example:
{code:sql}
SELECT '-1000-01-01'::DATE::VARCHAR = '1001-01-01 (BC)'
SELECT '3-01-01'::DATE::VARCHAR = '3-01-01'
{code}
As I understand BC/negative dates are not supported by Calcite currently
([CALCITE-5629|https://issues.apache.org/jira/browse/CALCITE-5629]).
{code:sql}
SELECT '1992/09/20'::DATE::VARCHAR = '1992-09-20'
{code}
Such format is not supported.
> Calcite. Fix numerous errors with DATE TIME types tests.
>
>
> Key: IGNITE-15619
> URL: https://issues.apache.org/jira/browse/IGNITE-15619
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
>
> for example :
> {noformat}
> statement ok
> CREATE TABLE dates(i DATE)
> statement ok
> INSERT INTO dates VALUES ('1993-08-14'), (NULL)
> {noformat}
> {noformat}
> statement ok
> CREATE TABLE times(i TIME)
> statement ok
> INSERT INTO times VALUES ('00:01:20'), ('20:08:10.998'), ('20:08:10.33'),
> ('20:08:10.001'), (NULL)
> {noformat}
> failed tests:
> {noformat}
> /types/date/*
> /types/time/*
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15619) Calcite. Fix numerous errors with DATE TIME types tests.
[
https://issues.apache.org/jira/browse/IGNITE-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832201#comment-17832201
]
Pavel Pereslegin edited comment on IGNITE-15619 at 3/29/24 3:12 PM:
The described example is related to IGNITE-15123 issue.
I think this issue mostly relates to different date formats and negative form.
For example:
{code:sql}
SELECT '-1000-01-01'::DATE::VARCHAR = '1001-01-01 (BC)'
SELECT '3-01-01'::DATE::VARCHAR = '3-01-01'
{code}
As I understand BC/negative dates are not supported by Calcite currently
([CALCITE-5629|https://issues.apache.org/jira/browse/CALCITE-5629]).
{code:sql}
SELECT '1992/09/20'::DATE::VARCHAR = '1992-09-20'
{code}
Such format is not supported.
was (Author: xtern):
The described example is related to IGNITE-15123 issue.
I think this issue mostly relates to different date formats and negative form.
For example:
{code:sql}
SELECT '-1000-01-01'::DATE::VARCHAR = '1001-01-01 (BC)'
{code}
As I understand BC/negative dates are not supported by Calcite currently
([CALCITE-5629|https://issues.apache.org/jira/browse/CALCITE-5629]).
{code:sql}
SELECT '1992/09/20'::DATE::VARCHAR = '1992-09-20'
{code}
Such format is not supported.
> Calcite. Fix numerous errors with DATE TIME types tests.
>
>
> Key: IGNITE-15619
> URL: https://issues.apache.org/jira/browse/IGNITE-15619
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
>
> for example :
> {noformat}
> statement ok
> CREATE TABLE dates(i DATE)
> statement ok
> INSERT INTO dates VALUES ('1993-08-14'), (NULL)
> {noformat}
> {noformat}
> statement ok
> CREATE TABLE times(i TIME)
> statement ok
> INSERT INTO times VALUES ('00:01:20'), ('20:08:10.998'), ('20:08:10.33'),
> ('20:08:10.001'), (NULL)
> {noformat}
> failed tests:
> {noformat}
> /types/date/*
> /types/time/*
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccUtils and cleanup enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-21835: --- Summary: Remove MvccUtils and cleanup enum RowData (was: Remove MvccUtils and unused MVCC classes from enum RowData) > Remove MvccUtils and cleanup enum RowData > - > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14602) Calcite engine. Wrong string representation of dates outside standard ISO range
[
https://issues.apache.org/jira/browse/IGNITE-14602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14602:
--
Description:
Subj.
Affected tests:
{{src/test/sql/types/date/date_parsing.test_ignored}}
{{src/test/sql/types/date/time_parsing.test_ignore}}
was:
Subj.
Affected tests:
{{src/test/sql/types/date/date_parsing.test_ignored}}
> Calcite engine. Wrong string representation of dates outside standard ISO
> range
>
>
> Key: IGNITE-14602
> URL: https://issues.apache.org/jira/browse/IGNITE-14602
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Minor
> Labels: calcite2-required, calcite3-required
>
> Subj.
> Affected tests:
> {{src/test/sql/types/date/date_parsing.test_ignored}}
> {{src/test/sql/types/date/time_parsing.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21891: Description: See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. * *deleteAll/removeAll* methods return key-only rows * *AbstractRowTupleAdapter* does not support key-only rows and always uses *positionInRow*. was: See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. *AbstractRowTupleAdapter* does not support key-only rows and always uses *positionInRow*. > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > * *deleteAll/removeAll* methods return key-only rows > * *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21891: Description: See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. *AbstractRowTupleAdapter* does not support key-only rows and always uses *positionInRow*. was:See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > *AbstractRowTupleAdapter* does not support key-only rows and always uses > *positionInRow*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21891: Labels: ignite-3 (was: ) > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
Pavel Tupitsyn created IGNITE-21891: --- Summary: deleteAll/removeAll does not work in embedded mode when key columns are after value Key: IGNITE-21891 URL: https://issues.apache.org/jira/browse/IGNITE-21891 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21891) deleteAll/removeAll does not work in embedded mode when key columns are after value
[ https://issues.apache.org/jira/browse/IGNITE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21891: Description: See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. > deleteAll/removeAll does not work in embedded mode when key columns are after > value > --- > > Key: IGNITE-21891 > URL: https://issues.apache.org/jira/browse/IGNITE-21891 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Fix For: 3.0.0-beta2 > > > See disabled tests in *ItCustomKeyColumnOrderEmbeddedTest*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18663) Sql. DATE Literals are not validated correctly.
[
https://issues.apache.org/jira/browse/IGNITE-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832213#comment-17832213
]
Pavel Pereslegin commented on IGNITE-18663:
---
looks like a duplicate of IGNITE-14602
> Sql. DATE Literals are not validated correctly.
> ---
>
> Key: IGNITE-18663
> URL: https://issues.apache.org/jira/browse/IGNITE-18663
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> Date literal with incorrect are not rejected. Some examples:
> {code:java}
> # month out of range
> INSERT INTO dates VALUES ('1993-20-14')
> # day out of range
> INSERT INTO dates VALUES ('1993-08-99')
> # day out of range because not a leapyear
> INSERT INTO dates VALUES ('1993-02-29')
> # day out of range because not a leapyear
> INSERT INTO dates VALUES ('1900-02-29')
> {code}
> See more examples in test_incorrect_dates.test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (IGNITE-21775) Lease grant message does not handle
[
https://issues.apache.org/jira/browse/IGNITE-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov closed IGNITE-21775.
--
> Lease grant message does not handle
> ---
>
> Key: IGNITE-21775
> URL: https://issues.apache.org/jira/browse/IGNITE-21775
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Runner_23864.log.zip
>
>
> h3. Motivation
> The lease grant message is sent to all primary replicas. After the message is
> applied, the replica prints (the example for repluication grout 8_part_9):
> {noformat}
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Received
> LeaseGrantedMessage for replica belonging to group=8_part_9, force=false
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Waiting for actual
> storage state, group=8_part_9
> [2024-03-17T00:13:16,473][INFO
> ][%isdst_n_1%JRaft-AppendEntries-Processor-8][ReplicaManager] Lease accepted
> [group=8_part_9, leaseStartTime=HybridTimestamp [physical=2024-03-17
> 00:13:16:471 +, logical=2, composite=112108135807123458]].
> {noformat}
> But the message is not present for repluication group 8_part_5:
> {noformat}
> Caused by: org.apache.ignite.internal.lang.IgniteInternalException:
> IGN-PLACEMENTDRIVER-1 TraceId:bd7944eb-5de7-401c-b721-4f6373de2b7d Failed to
> get the primary replica [tablePartitionId=8_part_5]
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:446)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.sql.engine.SqlQueryProcessor.lambda$primaryReplicas$2(SqlQueryProcessor.java:410)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
> at
> java.base@11.0.17/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base@11.0.17/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base@11.0.17/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ... 3 more
> {noformat}
> h3. Definition of done
> The lease grant message is handled for all replication groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21335) C++ 3.0: Implement JobExecutionOptions
[ https://issues.apache.org/jira/browse/IGNITE-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832212#comment-17832212 ] Pavel Tupitsyn commented on IGNITE-21335: - [~isapego] looks good to me. > C++ 3.0: Implement JobExecutionOptions > -- > > Key: IGNITE-21335 > URL: https://issues.apache.org/jira/browse/IGNITE-21335 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Igor Sapego >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Java part of this changes https://github.com/apache/ignite-3/pull/3050 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21775) Lease grant message does not handle
[
https://issues.apache.org/jira/browse/IGNITE-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov resolved IGNITE-21775.
Resolution: Duplicate
> Lease grant message does not handle
> ---
>
> Key: IGNITE-21775
> URL: https://issues.apache.org/jira/browse/IGNITE-21775
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Runner_23864.log.zip
>
>
> h3. Motivation
> The lease grant message is sent to all primary replicas. After the message is
> applied, the replica prints (the example for repluication grout 8_part_9):
> {noformat}
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Received
> LeaseGrantedMessage for replica belonging to group=8_part_9, force=false
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Waiting for actual
> storage state, group=8_part_9
> [2024-03-17T00:13:16,473][INFO
> ][%isdst_n_1%JRaft-AppendEntries-Processor-8][ReplicaManager] Lease accepted
> [group=8_part_9, leaseStartTime=HybridTimestamp [physical=2024-03-17
> 00:13:16:471 +, logical=2, composite=112108135807123458]].
> {noformat}
> But the message is not present for repluication group 8_part_5:
> {noformat}
> Caused by: org.apache.ignite.internal.lang.IgniteInternalException:
> IGN-PLACEMENTDRIVER-1 TraceId:bd7944eb-5de7-401c-b721-4f6373de2b7d Failed to
> get the primary replica [tablePartitionId=8_part_5]
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:446)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.sql.engine.SqlQueryProcessor.lambda$primaryReplicas$2(SqlQueryProcessor.java:410)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
> at
> java.base@11.0.17/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base@11.0.17/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base@11.0.17/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ... 3 more
> {noformat}
> h3. Definition of done
> The lease grant message is handled for all replication groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21890) AbstractSortedIndexStorageTest#testScan is flaky
Aleksandr Polovtcev created IGNITE-21890: Summary: AbstractSortedIndexStorageTest#testScan is flaky Key: IGNITE-21890 URL: https://issues.apache.org/jira/browse/IGNITE-21890 Project: Ignite Issue Type: Bug Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21775) Lease grant message does not handle
[
https://issues.apache.org/jira/browse/IGNITE-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832211#comment-17832211
]
Vladislav Pyatkov commented on IGNITE-21775:
The issue duplicates IGNITE-21566
> Lease grant message does not handle
> ---
>
> Key: IGNITE-21775
> URL: https://issues.apache.org/jira/browse/IGNITE-21775
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Runner_23864.log.zip
>
>
> h3. Motivation
> The lease grant message is sent to all primary replicas. After the message is
> applied, the replica prints (the example for repluication grout 8_part_9):
> {noformat}
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Received
> LeaseGrantedMessage for replica belonging to group=8_part_9, force=false
> [2024-03-17T00:13:16,472][INFO
> ][%isdst_n_1%MessagingService-inbound-0-0][ReplicaManager] Waiting for actual
> storage state, group=8_part_9
> [2024-03-17T00:13:16,473][INFO
> ][%isdst_n_1%JRaft-AppendEntries-Processor-8][ReplicaManager] Lease accepted
> [group=8_part_9, leaseStartTime=HybridTimestamp [physical=2024-03-17
> 00:13:16:471 +, logical=2, composite=112108135807123458]].
> {noformat}
> But the message is not present for repluication group 8_part_5:
> {noformat}
> Caused by: org.apache.ignite.internal.lang.IgniteInternalException:
> IGN-PLACEMENTDRIVER-1 TraceId:bd7944eb-5de7-401c-b721-4f6373de2b7d Failed to
> get the primary replica [tablePartitionId=8_part_5]
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:446)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:384)
> at
> app//org.apache.ignite.internal.sql.engine.SqlQueryProcessor.lambda$primaryReplicas$2(SqlQueryProcessor.java:410)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
> at
> java.base@11.0.17/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base@11.0.17/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base@11.0.17/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ... 3 more
> {noformat}
> h3. Definition of done
> The lease grant message is handled for all replication groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21890) AbstractSortedIndexStorageTest#testScan is flaky
[ https://issues.apache.org/jira/browse/IGNITE-21890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21890: - Fix Version/s: 3.0.0-beta2 > AbstractSortedIndexStorageTest#testScan is flaky > > > Key: IGNITE-21890 > URL: https://issues.apache.org/jira/browse/IGNITE-21890 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21887) Sql. Reuse caller thread if query already prepared
[ https://issues.apache.org/jira/browse/IGNITE-21887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21887: -- Fix Version/s: 3.0.0-beta2 > Sql. Reuse caller thread if query already prepared > -- > > Key: IGNITE-21887 > URL: https://issues.apache.org/jira/browse/IGNITE-21887 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > As of now, processing of the query unconditionally passed to the `sql-exec` > thread. Although such behavior is rather correct, it introduces additional > penalty in terms of increased latency. For short queries, like point lookup, > this latency in fact is longer than the time of operation itself. > To improve latency of short queries, let's reuse caller thread to initialize > query execution. It's important to make sure we are not hijacking caller > thread for long (on every stage of query initialization we either have to use > cached results, or pass the preparation to `sql-exec` thread). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-15619) Calcite. Fix numerous errors with DATE TIME types tests.
[
https://issues.apache.org/jira/browse/IGNITE-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832201#comment-17832201
]
Pavel Pereslegin commented on IGNITE-15619:
---
The described example is related to IGNITE-15123 issue.
I think this issue mostly relates to different date formats and negative form.
For example:
{code:sql}
SELECT '-1000-01-01'::DATE::VARCHAR = '1001-01-01 (BC)'
{code}
As I understand BC/negative dates are not supported by Calcite currently
([CALCITE-5629|https://issues.apache.org/jira/browse/CALCITE-5629]).
{code:sql}
SELECT '1992/09/20'::DATE::VARCHAR = '1992-09-20'
{code}
Such format is not supported.
> Calcite. Fix numerous errors with DATE TIME types tests.
>
>
> Key: IGNITE-15619
> URL: https://issues.apache.org/jira/browse/IGNITE-15619
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
>
> for example :
> {noformat}
> statement ok
> CREATE TABLE dates(i DATE)
> statement ok
> INSERT INTO dates VALUES ('1993-08-14'), (NULL)
> {noformat}
> {noformat}
> statement ok
> CREATE TABLE times(i TIME)
> statement ok
> INSERT INTO times VALUES ('00:01:20'), ('20:08:10.998'), ('20:08:10.33'),
> ('20:08:10.001'), (NULL)
> {noformat}
> failed tests:
> {noformat}
> /types/date/*
> /types/time/*
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21888) Remove MvccSnapshot
[ https://issues.apache.org/jira/browse/IGNITE-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21888: Ignite Flags: (was: Docs Required,Release Notes Required) > Remove MvccSnapshot > --- > > Key: IGNITE-21888 > URL: https://issues.apache.org/jira/browse/IGNITE-21888 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete MvccSnapshot functionality -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21889) Remove TxState
Julia Bakulina created IGNITE-21889: --- Summary: Remove TxState Key: IGNITE-21889 URL: https://issues.apache.org/jira/browse/IGNITE-21889 Project: Ignite Issue Type: Sub-task Reporter: Julia Bakulina Assignee: Julia Bakulina Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21888) Remove MvccSnapshot
[ https://issues.apache.org/jira/browse/IGNITE-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21888: Labels: ise (was: ) > Remove MvccSnapshot > --- > > Key: IGNITE-21888 > URL: https://issues.apache.org/jira/browse/IGNITE-21888 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete MvccSnapshot functionality -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21889) Remove TxState
[ https://issues.apache.org/jira/browse/IGNITE-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21889: Labels: ise (was: ) > Remove TxState > -- > > Key: IGNITE-21889 > URL: https://issues.apache.org/jira/browse/IGNITE-21889 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21889) Remove TxState
[ https://issues.apache.org/jira/browse/IGNITE-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21889: Ignite Flags: (was: Docs Required,Release Notes Required) > Remove TxState > -- > > Key: IGNITE-21889 > URL: https://issues.apache.org/jira/browse/IGNITE-21889 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccUtils and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Labels: ise (was: ) > Remove MvccUtils and unused MVCC classes from enum RowData > -- > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccUtils and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Ignite Flags: (was: Docs Required,Release Notes Required) > Remove MvccUtils and unused MVCC classes from enum RowData > -- > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21888) Remove MvccSnapshot
Julia Bakulina created IGNITE-21888: --- Summary: Remove MvccSnapshot Key: IGNITE-21888 URL: https://issues.apache.org/jira/browse/IGNITE-21888 Project: Ignite Issue Type: Sub-task Reporter: Julia Bakulina Assignee: Julia Bakulina Delete MvccSnapshot functionality -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccUtils and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Summary: Remove MvccUtils and unused MVCC classes from enum RowData (was: Remove unused MVCC classes from enum RowData) > Remove MvccUtils and unused MVCC classes from enum RowData > -- > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21887) Sql. Reuse caller thread if query already prepared
Konstantin Orlov created IGNITE-21887: - Summary: Sql. Reuse caller thread if query already prepared Key: IGNITE-21887 URL: https://issues.apache.org/jira/browse/IGNITE-21887 Project: Ignite Issue Type: Improvement Components: sql Reporter: Konstantin Orlov Assignee: Konstantin Orlov As of now, processing of the query unconditionally passed to the `sql-exec` thread. Although such behavior is rather correct, it introduces additional penalty in terms of increased latency. For short queries, like point lookup, this latency in fact is longer than the time of operation itself. To improve latency of short queries, let's reuse caller thread to initialize query execution. It's important to make sure we are not hijacking caller thread for long (on every stage of query initialization we either have to use cached results, or pass the preparation to `sql-exec` thread). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21885) AssertionError in RocksDbSortedIndexStorage
[
https://issues.apache.org/jira/browse/IGNITE-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832197#comment-17832197
]
Roman Puchkovskiy commented on IGNITE-21885:
The patch looks gorgeous to me
> AssertionError in RocksDbSortedIndexStorage
> ---
>
> Key: IGNITE-21885
> URL: https://issues.apache.org/jira/browse/IGNITE-21885
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{RocksDbSortedIndexStorage}} scan is actually broken, the following error is
> thrown when trying to call this method:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage.decodeRow(RocksDbSortedIndexStorage.java:207)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage$1.map(RocksDbSortedIndexStorage.java:196)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.rocksdb.index.AbstractRocksDbIndexStorage$UpToDatePeekCursor.lambda$next$0(AbstractRocksDbIndexStorage.java:323)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> {noformat}
> This happens because there's an assertion check that uses an incorrect
> partition ID offset inside of the index row. Existing tests are working only
> because we always use partition ID equal to 0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21884) Removal of MvccIO and MvccVersionAware
[ https://issues.apache.org/jira/browse/IGNITE-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-21884: --- Description: MvccIO and MvccVersionAware classes and corresponding code have to be removed. (was: MvccCoordinator class and corresponding code have to be removed.) > Removal of MvccIO and MvccVersionAware > -- > > Key: IGNITE-21884 > URL: https://issues.apache.org/jira/browse/IGNITE-21884 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > > MvccIO and MvccVersionAware classes and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Summary: Remove unused MVCC classes from enum RowData (was: Remove interface MvccIO and unused MVCC classes from enum RowData) > Remove unused MVCC classes from enum RowData > > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete interface MvccIO. > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Description: To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS was: To delete interface MvccIO. To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS > Remove unused MVCC classes from enum RowData > > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21886) Refactor CompressionProcessorImpl, move code partially to ignite-core module
Aleksey Plekhanov created IGNITE-21886: -- Summary: 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 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] [Updated] (IGNITE-21885) AssertionError in RocksDbSortedIndexStorage
[
https://issues.apache.org/jira/browse/IGNITE-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21885:
-
Description:
{{RocksDbSortedIndexStorage}} scan is actually broken, the following error is
thrown when trying to call this method:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage.decodeRow(RocksDbSortedIndexStorage.java:207)
~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage$1.map(RocksDbSortedIndexStorage.java:196)
~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.storage.rocksdb.index.AbstractRocksDbIndexStorage$UpToDatePeekCursor.lambda$next$0(AbstractRocksDbIndexStorage.java:323)
~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
{noformat}
This happens because there's an assertion check that uses an incorrect
partition ID offset inside of the index row. Existing tests are working only
because we always use partition ID equal to 0.
> AssertionError in RocksDbSortedIndexStorage
> ---
>
> Key: IGNITE-21885
> URL: https://issues.apache.org/jira/browse/IGNITE-21885
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> {{RocksDbSortedIndexStorage}} scan is actually broken, the following error is
> thrown when trying to call this method:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage.decodeRow(RocksDbSortedIndexStorage.java:207)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.rocksdb.index.RocksDbSortedIndexStorage$1.map(RocksDbSortedIndexStorage.java:196)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.rocksdb.index.AbstractRocksDbIndexStorage$UpToDatePeekCursor.lambda$next$0(AbstractRocksDbIndexStorage.java:323)
> ~[ignite-storage-rocksdb-3.0.0-SNAPSHOT.jar:?]
> {noformat}
> This happens because there's an assertion check that uses an incorrect
> partition ID offset inside of the index row. Existing tests are working only
> because we always use partition ID equal to 0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21885) AssertionError in RocksDbSortedIndexStorage
[ https://issues.apache.org/jira/browse/IGNITE-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21885: - Fix Version/s: 3.0.0-beta2 > AssertionError in RocksDbSortedIndexStorage > --- > > Key: IGNITE-21885 > URL: https://issues.apache.org/jira/browse/IGNITE-21885 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21885) AssertionError in RocksDbSortedIndexStorage
Aleksandr Polovtcev created IGNITE-21885: Summary: AssertionError in RocksDbSortedIndexStorage Key: IGNITE-21885 URL: https://issues.apache.org/jira/browse/IGNITE-21885 Project: Ignite Issue Type: Bug Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21288) C++ thin client: implement job execution interface
[
https://issues.apache.org/jira/browse/IGNITE-21288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832186#comment-17832186
]
Igor Sapego commented on IGNITE-21288:
--
Fixed findings. Merged to main.
> C++ thin client: implement job execution interface
> --
>
> Key: IGNITE-21288
> URL: https://issues.apache.org/jira/browse/IGNITE-21288
> Project: Ignite
> Issue Type: Improvement
> Components: compute, platforms, thin client
>Reporter: Vadim Pakhnushev
>Assignee: Igor Sapego
>Priority: Major
> Labels: ignite-3
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Implement {{JobExecution}} interface on the client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21745) BinaryTuple stores BigDecimal inefficiently
[
https://issues.apache.org/jira/browse/IGNITE-21745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832185#comment-17832185
]
Pavel Tupitsyn commented on IGNITE-21745:
-
Merged to main: 71c320f0af1a41045a19381e4e859cf38726342a
> BinaryTuple stores BigDecimal inefficiently
> ---
>
> Key: IGNITE-21745
> URL: https://issues.apache.org/jira/browse/IGNITE-21745
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> * While we have varint logic for short/int/long, we don't have it for
> BigDecimal.
> * MAX_DECIMAL_SCALE = Short.MAX_VALUE (CatalogUtils)
> As a result, we can waste multiple kilobytes to store a very simple value.
> {code:java}
> BigDecimal value = new BigDecimal(1);
> BinaryTupleBuilder builder = new BinaryTupleBuilder(1);
> ByteBuffer bytes = builder.appendDecimal(value,
> Short.MAX_VALUE).build();
> assertEquals(13610, bytes.limit());
> {code}
> This is especially a problem with some SQL queries which return values with
> MAX_DECIMAL_SCALE as a result of calculations, for example:
> {code:sql}
> select (cast(_T0.VAL as decimal(20, 10)) / ?) as DECIMAL0 from
> PUBLIC.TBL_INT32 as _T0
> {code}
> Another problem - .NET client can't read those large-scale values because of
> built-in type limitation. Even though the actual value is just *1*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccIO and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Summary: Remove MvccIO and unused MVCC classes from enum RowData (was: Remove unused MVCC classes from enum RowData) > Remove MvccIO and unused MVCC classes from enum RowData > --- > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove interface MvccIO and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Summary: Remove interface MvccIO and unused MVCC classes from enum RowData (was: Remove MvccIO and unused MVCC classes from enum RowData) > Remove interface MvccIO and unused MVCC classes from enum RowData > - > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete interface MvccIO. > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove MvccIO and unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Description: To delete interface MvccIO. To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS was: To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS > Remove MvccIO and unused MVCC classes from enum RowData > --- > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete interface MvccIO. > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Description: To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS was: To delete MVCC classes from package o.a.i.internal.pagemem.wal.record.* - DataPageMvccMarkUpdatedRecord - DataPageMvccUpdateNewTxStateHintRecord - DataPageMvccUpdateTxStateHintRecord - LazyMvccDataEntry - MvccDataEntry - MvccDataRecord - MvccTxRecord - UnwrapMvccDataEntry To delete MVCC classes from package o.a.i.internal.processors.cache.mvcc.* - MvccCoordinator - MvccFuture - MvccSnapshotFuture - MvccSnapshotResponseListener - MvccSnapshotWithoutTxs - MvccVersion - MvccVersionImpl > Remove unused MVCC classes from enum RowData > > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete unused Mvcc code from enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21835) Remove unused MVCC classes from enum RowData
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21835: Summary: Remove unused MVCC classes from enum RowData (was: Remove MVCC classes from package o.a.i.internal.processors.cache.mvcc) > Remove unused MVCC classes from enum RowData > > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > > To delete MVCC classes from package o.a.i.internal.pagemem.wal.record.* > - DataPageMvccMarkUpdatedRecord > - DataPageMvccUpdateNewTxStateHintRecord > - DataPageMvccUpdateTxStateHintRecord > - LazyMvccDataEntry > - MvccDataEntry > - MvccDataRecord > - MvccTxRecord > - UnwrapMvccDataEntry > > To delete MVCC classes from package o.a.i.internal.processors.cache.mvcc.* > - MvccCoordinator > - MvccFuture > - MvccSnapshotFuture > - MvccSnapshotResponseListener > - MvccSnapshotWithoutTxs > - MvccVersion > - MvccVersionImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21867) Add new ability to configure ReplicaService#RPC_TIMEOUT and TxMessageSender#RPC_TIMEOUT and increase the default values
[ https://issues.apache.org/jira/browse/IGNITE-21867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-21867: - Reviewer: Kirill Sizov > Add new ability to configure ReplicaService#RPC_TIMEOUT and > TxMessageSender#RPC_TIMEOUT and increase the default values > --- > > Key: IGNITE-21867 > URL: https://issues.apache.org/jira/browse/IGNITE-21867 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > h3. Motivation > RPC_TIMEOUT was mistakenly recognized as a network layer timeout, but > actually it's a business operation one. Within the context of replicaService, > there are legitimate reasons for operation to be processed longer than > current timeout of 3 seconds, basically it should be possible to wait > indefinitely until the transaction times out. But because we don't have > transaction timeout and because of possible bugs it seems reasonable to have > an operation processing timeout "watchdog" with finite but relatively big > configurable value. > h3. Definition of Done > * Add ability to configure ReplicaService#RPC_TIMEOUT and > TxMessageSender#RPC_TIMEOUT and increase the default values. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21875) SQL API cleanup - remove properties and reactive methods
[ https://issues.apache.org/jira/browse/IGNITE-21875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832177#comment-17832177 ] Igor Sapego commented on IGNITE-21875: -- Looks good to me. > SQL API cleanup - remove properties and reactive methods > > > Key: IGNITE-21875 > URL: https://issues.apache.org/jira/browse/IGNITE-21875 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > * *Statement#properties* are not used > * Reactive APIs are not implemented > Remove them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21884) Removal of MvccIO and MvccVersionAware
[ https://issues.apache.org/jira/browse/IGNITE-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov reassigned IGNITE-21884: -- Assignee: Ilya Shishkov > Removal of MvccIO and MvccVersionAware > -- > > Key: IGNITE-21884 > URL: https://issues.apache.org/jira/browse/IGNITE-21884 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > > MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21884) Removal of MvccIO and MvccVersionAware
[ https://issues.apache.org/jira/browse/IGNITE-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov reassigned IGNITE-21884: -- Assignee: (was: Oleg Valuyskiy) > Removal of MvccIO and MvccVersionAware > -- > > Key: IGNITE-21884 > URL: https://issues.apache.org/jira/browse/IGNITE-21884 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Priority: Minor > Labels: ise > > MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21884) Removal of MvccIO and MvccVersionAware
Ilya Shishkov created IGNITE-21884: -- Summary: Removal of MvccIO and MvccVersionAware Key: IGNITE-21884 URL: https://issues.apache.org/jira/browse/IGNITE-21884 Project: Ignite Issue Type: Sub-task Components: mvcc Reporter: Ilya Shishkov Assignee: Oleg Valuyskiy MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21883) s390x support to Teamcity CI
Sangita Nalkar created IGNITE-21883: --- Summary: s390x support to Teamcity CI Key: IGNITE-21883 URL: https://issues.apache.org/jira/browse/IGNITE-21883 Project: Ignite Issue Type: New Feature Components: general Affects Versions: None Environment: s390x Architecture Reporter: Sangita Nalkar Fix For: None Hello, Wanted to know if it could be possible to add s390x architecture support to Teamcity CI for Apache Ignite. Please let me know if there is something I can do at my end to help add the support to CI. We can provide s390x infra support as well if required. Regards, Sangita -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21882) Improve metastorage processing of large records
Kirill Tkalenko created IGNITE-21882: Summary: Improve metastorage processing of large records Key: IGNITE-21882 URL: https://issues.apache.org/jira/browse/IGNITE-21882 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Fix For: 3.0.0-beta2 >From IGNITE-21142 there is an assumption that when frequently working with >large records, the metastorage begins to process such commands longer, which >leads to long processing of its commands. We need to improve this, I don’t >know how yet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21881) Deal with retry send metastorage raft commands after a timeout
[ https://issues.apache.org/jira/browse/IGNITE-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-21881: - Fix Version/s: 3.0.0-beta2 > Deal with retry send metastorage raft commands after a timeout > -- > > Key: IGNITE-21881 > URL: https://issues.apache.org/jira/browse/IGNITE-21881 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > As a result of the analysis and reproduction of IGNITE-21142, it was found > that the metastorage raft command can be re-sent if it does not time out, > which may not be good and lead to hidden negative consequences, such as in > IGNITE-21142. > Here we need to find out the reasons for this decision (with re-try by > timeout) and understand what to do next. I think we should use an infinite > timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21881) Deal with retry send metastorage raft commands after a timeout
[ https://issues.apache.org/jira/browse/IGNITE-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-21881: - Labels: ignite-3 (was: ) > Deal with retry send metastorage raft commands after a timeout > -- > > Key: IGNITE-21881 > URL: https://issues.apache.org/jira/browse/IGNITE-21881 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > > As a result of the analysis and reproduction of IGNITE-21142, it was found > that the metastorage raft command can be re-sent if it does not time out, > which may not be good and lead to hidden negative consequences, such as in > IGNITE-21142. > Here we need to find out the reasons for this decision (with re-try by > timeout) and understand what to do next. I think we should use an infinite > timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21881) Deal with retry send metastorage raft commands after a timeout
Kirill Tkalenko created IGNITE-21881: Summary: Deal with retry send metastorage raft commands after a timeout Key: IGNITE-21881 URL: https://issues.apache.org/jira/browse/IGNITE-21881 Project: Ignite Issue Type: Bug Reporter: Kirill Tkalenko As a result of the analysis and reproduction of IGNITE-21142, it was found that the metastorage raft command can be re-sent if it does not time out, which may not be good and lead to hidden negative consequences, such as in IGNITE-21142. Here we need to find out the reasons for this decision (with re-try by timeout) and understand what to do next. I think we should use an infinite timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21818) Broadcasting job that returns null fails
[
https://issues.apache.org/jira/browse/IGNITE-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21818:
---
Priority: Blocker (was: Major)
> Broadcasting job that returns null fails
>
>
> Key: IGNITE-21818
> URL: https://issues.apache.org/jira/browse/IGNITE-21818
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Vadim Pakhnushev
>Assignee: Roman Puchkovskiy
>Priority: Blocker
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Running the job which returns null as a result via
> IgniteCompute.executeBroadcastAsync or executeBroadcast fails with the NPE:
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at java.base/java.util.Objects.requireNonNull(Objects.java:221)
> at
> java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:178)
> at
> java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.base/java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1764)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> org.apache.ignite.compute.IgniteCompute.lambda$executeBroadcastAsync$3(IgniteCompute.java:508)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.compute.IgniteCompute.executeBroadcastAsync(IgniteCompute.java:507)
> at
> org.apache.ignite.compute.IgniteCompute.executeBroadcastAsync(IgniteCompute.java:529)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21880) Data region definitions are ignored on Ignite startup
[
https://issues.apache.org/jira/browse/IGNITE-21880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Myskov updated IGNITE-21880:
---
Description:
On Ignite startup, only the default data region is created.
In the provided configuration example, region1 and region2 will be ignored:
{code:java}
aimem {
defaultRegion {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
regions {
region1 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
region2 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
}
pageSize=16384
}
{code}
However, if regions are added after the cluster initialization, regions will be
created. This happens because VolatilePageMemoryStorageEngine.start() creates
default data regions and starts listening for configuration changes but ignores
data regions that already exist.
The following storage engines are affected:
* VolatilePageMemoryStorageEngine
* PersistentPageMemoryStorageEngine
* RocksDbStorageEngine
was:
On Ignite startup, only the default data region is created.
In the provided configuration example, region1 and region2 will be ignored:
{code:java}
aimem {
defaultRegion {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268 435 456
memoryAllocator {
type=unsafe
}
}
regions {
region1 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
region2 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
}
pageSize=16384
}
{code}
However, if regions are added after the cluster initialization, regions will be
created. This happens because VolatilePageMemoryStorageEngine.start() creates
default data regions and starts listening for configuration changes but ignores
data regions that already exist.
The following storage engines are affected:
* VolatilePageMemoryStorageEngine
* PersistentPageMemoryStorageEngine
* RocksDbStorageEngine
> Data region definitions are ignored on Ignite startup
> -
>
> Key: IGNITE-21880
> URL: https://issues.apache.org/jira/browse/IGNITE-21880
> Project: Ignite
> Issue Type: Bug
>Reporter: Maksim Myskov
>Priority: Major
> Labels: ignite-3
>
> On Ignite startup, only the default data region is created.
> In the provided configuration example, region1 and region2 will be ignored:
> {code:java}
> aimem {
> defaultRegion {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> regions {
> region1 {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> region2 {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> }
> pageSize=16384
> }
> {code}
> However, if regions are added after the cluster initialization, regions will
> be created. This happens because VolatilePageMemoryStorageEngine.start()
> creates default data regions and starts listening for configuration changes
> but ignores data regions that already exist.
> The following storage engines are affected:
> * VolatilePageMemoryStorageEngine
> * PersistentPageMemoryStorageEngine
> * RocksDbStorageEngine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21880) Data region definitions are ignored on Ignite startup
Maksim Myskov created IGNITE-21880:
--
Summary: Data region definitions are ignored on Ignite startup
Key: IGNITE-21880
URL: https://issues.apache.org/jira/browse/IGNITE-21880
Project: Ignite
Issue Type: Bug
Reporter: Maksim Myskov
On Ignite startup, only the default data region is created.
In the provided configuration example, region1 and region2 will be ignored:
{code:java}
aimem {
defaultRegion {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268 435 456
memoryAllocator {
type=unsafe
}
}
regions {
region1 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
region2 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
}
pageSize=16384
}
{code}
However, if regions are added after the cluster initialization, regions will be
created. This happens because VolatilePageMemoryStorageEngine.start() creates
default data regions and starts listening for configuration changes but ignores
data regions that already exist.
The following storage engines are affected:
* VolatilePageMemoryStorageEngine
* PersistentPageMemoryStorageEngine
* RocksDbStorageEngine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21256) Internal API for local partition states
[ https://issues.apache.org/jira/browse/IGNITE-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-21256: - Reviewer: Kirill Tkalenko > Internal API for local partition states > --- > > Key: IGNITE-21256 > URL: https://issues.apache.org/jira/browse/IGNITE-21256 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Please refer to https://issues.apache.org/jira/browse/IGNITE-21140 for the > list. We need an API (with implementation) to access the list of local > partitions and their states. The way to determine them: > * comparing current assignments with replica states > * check the state machine, it might be broken or installing snapshot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21874) Log Java versions to the server log at startup
[
https://issues.apache.org/jira/browse/IGNITE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832171#comment-17832171
]
Alexander Belyak commented on IGNITE-21874:
---
Related to the IGNITE-19383
> Log Java versions to the server log at startup
> -
>
> Key: IGNITE-21874
> URL: https://issues.apache.org/jira/browse/IGNITE-21874
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 3.0.0-alpha5
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> We need to log some environments to the server log.
> 1) *OS* and {*}Java version{*}:
> AI2:
> {noformat}
> OS: Linux 5.15.0-100-generic amd64
> [17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
> AI3:
> {code:java}
> // Nothing
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21818) Broadcasting job that returns null fails
[
https://issues.apache.org/jira/browse/IGNITE-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy reassigned IGNITE-21818:
--
Assignee: Roman Puchkovskiy (was: Vadim Pakhnushev)
> Broadcasting job that returns null fails
>
>
> Key: IGNITE-21818
> URL: https://issues.apache.org/jira/browse/IGNITE-21818
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Vadim Pakhnushev
>Assignee: Roman Puchkovskiy
>Priority: Major
> Labels: ignite-3
>
> Running the job which returns null as a result via
> IgniteCompute.executeBroadcastAsync or executeBroadcast fails with the NPE:
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at java.base/java.util.Objects.requireNonNull(Objects.java:221)
> at
> java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:178)
> at
> java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.base/java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1764)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> org.apache.ignite.compute.IgniteCompute.lambda$executeBroadcastAsync$3(IgniteCompute.java:508)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.compute.IgniteCompute.executeBroadcastAsync(IgniteCompute.java:507)
> at
> org.apache.ignite.compute.IgniteCompute.executeBroadcastAsync(IgniteCompute.java:529)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-21874) Log Java versions to the server log at startup
[
https://issues.apache.org/jira/browse/IGNITE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832171#comment-17832171
]
Alexander Belyak edited comment on IGNITE-21874 at 3/29/24 10:53 AM:
-
Related to the IGNITE-19383 Add commit hash to the server log
was (Author: berkov):
Related to the IGNITE-19383
> Log Java versions to the server log at startup
> -
>
> Key: IGNITE-21874
> URL: https://issues.apache.org/jira/browse/IGNITE-21874
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 3.0.0-alpha5
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> We need to log some environments to the server log.
> 1) *OS* and {*}Java version{*}:
> AI2:
> {noformat}
> OS: Linux 5.15.0-100-generic amd64
> [17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
> AI3:
> {code:java}
> // Nothing
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19383) Add commit hash to the server log
[
https://issues.apache.org/jira/browse/IGNITE-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-19383:
--
Summary: Add commit hash to the server log (was: Add commit hash to log)
> Add commit hash to the server log
> -
>
> Key: IGNITE-19383
> URL: https://issues.apache.org/jira/browse/IGNITE-19383
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> Let's add commit hash into the log message:
>
> {code:java}
> INFO:
> # ___ __
> ### / | _ _ / /_ ___
> # # / /| | / __ \ / __ `// ___// __ \ / _ \
> ### ## / ___ | / /_/ // /_/ // /__ / / / // ___/
> # ### /_/ |_|/ .___/ \__,_/ \___//_/ /_/ \___/
> ### ## /_/
> _ __ _
> # ## / _/ _ (_)/ /_ ___ |__ /
> ### # / / / __ `// __ \ / // __// _ \ /_ <
> # # _/ / / /_/ // / / // // /_ / ___/ ___/ /
> ## /___/ \__, //_/ /_//_/ \__/ \___/ //
> ## //
> Apache Ignite ver. 3.0.0-SNAPSHOT
> {code}
> after the version like in the previous version
> AI2 (version and commit has):
> {noformat}
> ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
> AI3 (only version):
> {noformat}
> Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19383) Add commit hash to log
[
https://issues.apache.org/jira/browse/IGNITE-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832170#comment-17832170
]
Alexander Belyak commented on IGNITE-19383:
---
Related to the IGNITE-21874
> Add commit hash to log
> --
>
> Key: IGNITE-19383
> URL: https://issues.apache.org/jira/browse/IGNITE-19383
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> Let's add commit hash into the log message:
>
> {code:java}
> INFO:
> # ___ __
> ### / | _ _ / /_ ___
> # # / /| | / __ \ / __ `// ___// __ \ / _ \
> ### ## / ___ | / /_/ // /_/ // /__ / / / // ___/
> # ### /_/ |_|/ .___/ \__,_/ \___//_/ /_/ \___/
> ### ## /_/
> _ __ _
> # ## / _/ _ (_)/ /_ ___ |__ /
> ### # / / / __ `// __ \ / // __// _ \ /_ <
> # # _/ / / /_/ // / / // // /_ / ___/ ___/ /
> ## /___/ \__, //_/ /_//_/ \__/ \___/ //
> ## //
> Apache Ignite ver. 3.0.0-SNAPSHOT
> {code}
> after the version like in the previous version
> AI2 (version and commit has):
> {noformat}
> ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
> AI3 (only version):
> {noformat}
> Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21879:
--
Fix Version/s: 3.0.0-beta2
> Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
> -
>
> Key: IGNITE-21879
> URL: https://issues.apache.org/jira/browse/IGNITE-21879
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Example
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware
> {code}
> org.opentest4j.AssertionFailedError: expected: <0> but was: <-1>
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at
> app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:531)
> at
> app//org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery(ItJdbcStatementSelfTest.java:824)
> at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21879:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
> -
>
> Key: IGNITE-21879
> URL: https://issues.apache.org/jira/browse/IGNITE-21879
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: ignite-3
>
> Example
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware
> {code}
> org.opentest4j.AssertionFailedError: expected: <0> but was: <-1>
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at
> app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:531)
> at
> app//org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery(ItJdbcStatementSelfTest.java:824)
> at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21874) Log Java versions to the server log at startup
[
https://issues.apache.org/jira/browse/IGNITE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-21874:
--
Summary: Log Java versions to the server log at startup (was: Log
versions (java, ignite) to the server log at startup)
> Log Java versions to the server log at startup
> -
>
> Key: IGNITE-21874
> URL: https://issues.apache.org/jira/browse/IGNITE-21874
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 3.0.0-alpha5
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> We need to log some environments to the server log.
> 1) *OS* and {*}Java version{*}:
> AI2:
> {noformat}
> OS: Linux 5.15.0-100-generic amd64
> [17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
> AI3:
> {code:java}
> // Nothing
> {code}
> 2) Product version WITH *commit hash*
> AI2 (version and commit has):
> {noformat}
> ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
> AI3 (only version):
> {noformat}
> Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
Maksim Zhuravkov created IGNITE-21879: - Summary: Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky Key: IGNITE-21879 URL: https://issues.apache.org/jira/browse/IGNITE-21879 Project: Ignite Issue Type: Bug Components: sql Reporter: Maksim Zhuravkov Example https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[ https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21879: -- Labels: ignite-3 (was: ) > Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky > - > > Key: IGNITE-21879 > URL: https://issues.apache.org/jira/browse/IGNITE-21879 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > Example > https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19383) Add commit hash to log
[
https://issues.apache.org/jira/browse/IGNITE-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-19383:
--
Description:
Let's add commit hash into the log message:
{code:java}
INFO:
# ___ __
### / | _ _ / /_ ___
# # / /| | / __ \ / __ `// ___// __ \ / _ \
### ## / ___ | / /_/ // /_/ // /__ / / / // ___/
# ### /_/ |_|/ .___/ \__,_/ \___//_/ /_/ \___/
### ## /_/
_ __ _
# ## / _/ _ (_)/ /_ ___ |__ /
### # / / / __ `// __ \ / // __// _ \ /_ <
# # _/ / / /_/ // / / // // /_ / ___/ ___/ /
## /___/ \__, //_/ /_//_/ \__/ \___/ //
## //
Apache Ignite ver. 3.0.0-SNAPSHOT
{code}
after the version like in the previous version
AI2 (version and commit has):
{noformat}
ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
AI3 (only version):
{noformat}
Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
was:
Let's add commit hash into the log message:
{code:java}
INFO:
# ___ __
### / | _ _ / /_ ___
# # / /| | / __ \ / __ `// ___// __ \ / _ \
### ## / ___ | / /_/ // /_/ // /__ / / / // ___/
# ### /_/ |_|/ .___/ \__,_/ \___//_/ /_/ \___/
### ## /_/
_ __ _
# ## / _/ _ (_)/ /_ ___ |__ /
### # / / / __ `// __ \ / // __// _ \ /_ <
# # _/ / / /_/ // / / // // /_ / ___/ ___/ /
## /___/ \__, //_/ /_//_/ \__/ \___/ //
## //
Apache Ignite ver. 3.0.0-SNAPSHOT
{code}
after the version
> Add commit hash to log
> --
>
> Key: IGNITE-19383
> URL: https://issues.apache.org/jira/browse/IGNITE-19383
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> Let's add commit hash into the log message:
>
> {code:java}
> INFO:
> # ___ __
> ### / | _ _ / /_ ___
> # # / /| | / __ \ / __ `// ___// __ \ / _ \
> ### ## / ___ | / /_/ // /_/ // /__ / / / // ___/
> # ### /_/ |_|/ .___/ \__,_/ \___//_/ /_/ \___/
> ### ## /_/
> _ __ _
> # ## / _/ _ (_)/ /_ ___ |__ /
> ### # / / / __ `// __ \ / // __// _ \ /_ <
> # # _/ / / /_/ // / / // // /_ / ___/ ___/ /
> ## /___/ \__, //_/ /_//_/ \__/ \___/ //
> ## //
> Apache Ignite ver. 3.0.0-SNAPSHOT
> {code}
> after the version like in the previous version
> AI2 (version and commit has):
> {noformat}
> ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
> AI3 (only version):
> {noformat}
> Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21879:
--
Description:
Example
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware
{code}
org.opentest4j.AssertionFailedError: expected: <0> but was: <-1>
at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at
app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:531)
at
app//org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery(ItJdbcStatementSelfTest.java:824)
at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
{code}
was:Example
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware
> Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
> -
>
> Key: IGNITE-21879
> URL: https://issues.apache.org/jira/browse/IGNITE-21879
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: ignite-3
>
> Example
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleJdbc/7983383?hideTestsFromDependencies=false=false=false=true=true=true=7983383_2435_86.2416.2435=debug=flowAware
> {code}
> org.opentest4j.AssertionFailedError: expected: <0> but was: <-1>
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at
> app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:531)
> at
> app//org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery(ItJdbcStatementSelfTest.java:824)
> at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21874) Log Java versions to the server log at startup
[
https://issues.apache.org/jira/browse/IGNITE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-21874:
--
Description:
We need to log some environments to the server log.
1) *OS* and {*}Java version{*}:
AI2:
{noformat}
OS: Linux 5.15.0-100-generic amd64
[17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
AI3:
{code:java}
// Nothing
{code}
was:
We need to log some environments to the server log.
1) *OS* and {*}Java version{*}:
AI2:
{noformat}
OS: Linux 5.15.0-100-generic amd64
[17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
AI3:
{code:java}
// Nothing
{code}
2) Product version WITH *commit hash*
AI2 (version and commit has):
{noformat}
ver. 2.16.0#20231215-sha1:7bde6a42{noformat}
AI3 (only version):
{noformat}
Apache Ignite ver. 3.0.0-SNAPSHOT{noformat}
> Log Java versions to the server log at startup
> -
>
> Key: IGNITE-21874
> URL: https://issues.apache.org/jira/browse/IGNITE-21874
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 3.0.0-alpha5
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> We need to log some environments to the server log.
> 1) *OS* and {*}Java version{*}:
> AI2:
> {noformat}
> OS: Linux 5.15.0-100-generic amd64
> [17:54:06] VM information: Java(TM) SE Runtime Environment 18.0.1.1+2-6
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 18.0.1.1+2-6{noformat}
> AI3:
> {code:java}
> // Nothing
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21861) Unexpected "Transaction is already finished" exception
[
https://issues.apache.org/jira/browse/IGNITE-21861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832169#comment-17832169
]
Kirill Sizov commented on IGNITE-21861:
Seems like a command was trying to execute on a finished transaction, hard to
say COMMITTED or ABORTED.
> Unexpected "Transaction is already finished" exception
> ---
>
> Key: IGNITE-21861
> URL: https://issues.apache.org/jira/browse/IGNITE-21861
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_SQL_Engine_4133_.log
>
>
> Exception in log:
> {code:java}
> [2024-03-27T01:24:46,636][WARN
> ][%idt_n_1%partition-operations-4][ReplicaManager] Failed to process replica
> request [request=ReadWriteScanRetrieveBatchReplicaRequestImpl [batchSize=512,
> columnsToInclude=null, commitPartitionId=TablePartitionIdMessageImpl
> [partitionId=17, tableId=90],
> coordinatorId=125b397c-0404-4dcf-a28b-625fe010ecef,
> enlistmentConsistencyToken=112165039282455690, exactKey=null, flags=0,
> full=false, groupId=92_part_7, indexToUse=null, lowerBoundPrefix=null,
> scanId=20361, timestampLong=112165039967305730,
> transactionId=018e7d82-647b-0030-63a2-6a190001, upperBoundPrefix=null]].
> java.util.concurrent.CompletionException:
> org.apache.ignite.tx.TransactionException: IGN-TX-14
> TraceId:6612dad8-4a32-4453-8af0-0139e336aad9 Transaction is already finished.
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1099)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequest(PartitionReplicaListener.java:660)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequestWithTxRwCounter(PartitionReplicaListener.java:3860)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$5(PartitionReplicaListener.java:436)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> [?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
> [?:?]
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
> [?:?]
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> [?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.base/java.lang.Thread.run(Thread.java:834) [?:?]
> Caused by: org.apache.ignite.tx.TransactionException: Transaction is already
> finished.
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1937)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequest(PartitionReplicaListener.java:659)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> ... 10 more{code}
>
> It happens in PartitionReplicaListener because the local volatile tx state is
> null or final when trying to compute a value for txCleanupReadyFutures map:
> {code:java}
> txCleanupReadyFutures.compute(txId, (id, txOps) -> {
> // First check whether the transaction has already been finished.
> // And complete cleanupReadyFut with exception if it is the case.
> TxStateMeta txStateMeta = txManager.stateMeta(txId);
> if (txStateMeta == null || isFinalState(txStateMeta.txState())) {
> cleanupReadyFut.completeExceptionally(new Exception());
> return txOps;
> }
> // Otherwise collect cleanupReadyFut in the transaction's futures.
> if (txOps == null) {
> txOps = new TxCleanupReadyFutureList();
> }
> txOps.futures.computeIfAbsent(cmdType, type -> new HashMap<>()).put(opId,
> cleanupReadyFut);
> return txOps;
> });
> if (cleanupReadyFut.isCompletedExceptionally()) {
> return failedFuture(new TransactionException(TX_ALREADY_FINISHED_ERR,
> "Transaction is already finished."));
>
[jira] [Commented] (IGNITE-17591) Refactor toString generation for network messages
[ https://issues.apache.org/jira/browse/IGNITE-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832166#comment-17832166 ] Philipp Shergalis commented on IGNITE-17591: S.toString already trims big arrays (retaining first 100 elements) and huge strings (leaving only 1 symbols, head and tail). So adding only possibility to hide sensitive info > Refactor toString generation for network messages > - > > Key: IGNITE-17591 > URL: https://issues.apache.org/jira/browse/IGNITE-17591 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Semyon Danilov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > toString method generation for the network message should be taking into > account several things: > 1) Message may contain large objects (such as byte arrays) > 2) Some data can be sensitive, so it should be possible to ignore or mask a > field in the toString method -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18656) Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
[
https://issues.apache.org/jira/browse/IGNITE-18656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832149#comment-17832149
]
Maksim Zhuravkov commented on IGNITE-18656:
---
Fixed in IGNITE-18671. Tests related to this issue should pass but
{code:java}
# overflow in conversion
skipif ignite3
# https://issues.apache.org/jira/browse/IGNITE-18656
statement error
SELECT '9223372036854788.758'::DECIMAL;
{code}
Should be changed to because this cast is valid.
{code:java}
# no overflow in conversion
query I
SELECT '9223372036854788.758'::DECIMAL;
9223372036854788.758
{code}
> Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
>
>
> Key: IGNITE-18656
> URL: https://issues.apache.org/jira/browse/IGNITE-18656
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> # overflow in conversion
> skipif ignite3
> statement error
> SELECT '9223372036854788.758'::DECIMAL; {code}
> {code:java}
> Not expected result at: (test_decimal.test:40). Statement: SELECT
> '9223372036854788.758'::DECIMAL;. Error: an instance of java.lang.String ==>
> Expected java.lang.Throwable to be thrown, but nothing was thrown.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-18656) Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
[
https://issues.apache.org/jira/browse/IGNITE-18656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832149#comment-17832149
]
Maksim Zhuravkov edited comment on IGNITE-18656 at 3/29/24 10:27 AM:
-
Fixed in IGNITE-18671. Tests related to this issue should pass but
{code:java}
# overflow in conversion
skipif ignite3
# https://issues.apache.org/jira/browse/IGNITE-18656
statement error
SELECT '9223372036854788.758'::DECIMAL;
{code}
Should be changed to because this cast is valid (?).
{code:java}
# no overflow in conversion
query I
SELECT '9223372036854788.758'::DECIMAL;
9223372036854788.758
{code}
was (Author: JIRAUSER298618):
Fixed in IGNITE-18671. Tests related to this issue should pass but
{code:java}
# overflow in conversion
skipif ignite3
# https://issues.apache.org/jira/browse/IGNITE-18656
statement error
SELECT '9223372036854788.758'::DECIMAL;
{code}
Should be changed to because this cast is valid.
{code:java}
# no overflow in conversion
query I
SELECT '9223372036854788.758'::DECIMAL;
9223372036854788.758
{code}
> Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
>
>
> Key: IGNITE-18656
> URL: https://issues.apache.org/jira/browse/IGNITE-18656
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> # overflow in conversion
> skipif ignite3
> statement error
> SELECT '9223372036854788.758'::DECIMAL; {code}
> {code:java}
> Not expected result at: (test_decimal.test:40). Statement: SELECT
> '9223372036854788.758'::DECIMAL;. Error: an instance of java.lang.String ==>
> Expected java.lang.Throwable to be thrown, but nothing was thrown.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-18671) Sql. Cast to BigInt with overflow does not produce an error.
[
https://issues.apache.org/jira/browse/IGNITE-18671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832136#comment-17832136
]
Maksim Zhuravkov edited comment on IGNITE-18671 at 3/29/24 10:16 AM:
-
Resolved in IGNITE-18662. This test fails (as expected) with BIGINT out of
range error.
The test is located in test_sum.test
was (Author: JIRAUSER298618):
Resolved in IGNITE-18662. Test fails (as expected) with BIGINT out of range
error
> Sql. Cast to BigInt with overflow does not produce an error.
>
>
> Key: IGNITE-18671
> URL: https://issues.apache.org/jira/browse/IGNITE-18671
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Environment: See test_sum.test
> Query
>Reporter: Maksim Zhuravkov
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> CREATE TABLE bigints(b BIGINT);
> # a bunch of huge values
> statement ok
> INSERT INTO bigints SELECT * FROM table(system_range(4611686018427387904,
> 4611686018427388903, 1));
> # this is too big for a bigint.
> # should fail but returns the result below
> query I
> SELECT SUM(b)::BIGINT FROM bigints
>
> 499500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18671) Sql. Cast to BigInt with overflow does not produce an error.
[
https://issues.apache.org/jira/browse/IGNITE-18671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832136#comment-17832136
]
Maksim Zhuravkov commented on IGNITE-18671:
---
Resolved in IGNITE-18662. Test fails (as expected) with BIGINT out of range
error
> Sql. Cast to BigInt with overflow does not produce an error.
>
>
> Key: IGNITE-18671
> URL: https://issues.apache.org/jira/browse/IGNITE-18671
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Environment: See test_sum.test
> Query
>Reporter: Maksim Zhuravkov
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> CREATE TABLE bigints(b BIGINT);
> # a bunch of huge values
> statement ok
> INSERT INTO bigints SELECT * FROM table(system_range(4611686018427387904,
> 4611686018427388903, 1));
> # this is too big for a bigint.
> # should fail but returns the result below
> query I
> SELECT SUM(b)::BIGINT FROM bigints
>
> 499500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21657) Sql. SqlTestUtils::assertThrowsSqlException reports misleading error message
[ https://issues.apache.org/jira/browse/IGNITE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832131#comment-17832131 ] Maksim Zhuravkov commented on IGNITE-21657: --- Resolved in IGNITE-21452 > Sql. SqlTestUtils::assertThrowsSqlException reports misleading error message > > > Key: IGNITE-21657 > URL: https://issues.apache.org/jira/browse/IGNITE-21657 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Trivial > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > The condition in error reporting is misleading, it should display a error > message when a message does not match, but it displays error codes (which > match). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21862) Rename table catalog command must also rename the PK index
[
https://issues.apache.org/jira/browse/IGNITE-21862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21862:
-
Fix Version/s: 3.0.0-beta2
> Rename table catalog command must also rename the PK index
> --
>
> Key: IGNITE-21862
> URL: https://issues.apache.org/jira/browse/IGNITE-21862
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{RenameTableCommand}} is used to rename a table. However, it does not rename
> its primary key, which is tied to the table's name. This leads to a bug, for
> example, when you rename a table and create a new table with the old name an
> exception is thrown indicating that an index with this name already exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
