[jira] [Updated] (IGNITE-21656) Cache dump fails on a cache with a node filter.
[
https://issues.apache.org/jira/browse/IGNITE-21656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-21656:
--
Fix Version/s: 2.17
> Cache dump fails on a cache with a node filter.
> ---
>
> Key: IGNITE-21656
> URL: https://issues.apache.org/jira/browse/IGNITE-21656
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Ignite may fail to create dump of cache with a node filter.
> 1) If there are no partitions on some node, we assign the empty set as the
> snapshot task result:
> {code:java}
> if (parts.isEmpty() && !withMetaStorage)
> task0 = new GridFinishedFuture<>(Collections.emptySet());
> else {
> ...
> }
> {code}
> Cache dump doesn't contain the metastorage. Further, we may cast the result to
> {code:java}
> SnapshotFutureTaskResult res = (SnapshotFutureTaskResult)task0.result();
> {code}
> but it is a
> {code:java}
> Collections#EMPTY_SET
> {code}
> Stacktrace:
> {code:java}
> [ERROR][snapshot-runner-#413%dump.IgniteCacheDumpSelfTest0%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.lang.ClassCastException: class
> java.util.Collections$EmptySet cannot be cast to class
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> (java.util.Collections$EmptySet is in module java.base of loader 'bootstrap';
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult is in
> unnamed module of loader 'app')]]
> java.lang.ClassCastException: class java.util.Collections$EmptySet cannot be
> cast to class
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> (java.util.Collections$EmptySet is in module java.base of loader
> 'bootstrap';
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> is in unnamed module of loader 'app')
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.lambda$initLocalFullSnapshot$923db49$1(IgniteSnapshotManager.java:1221)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$d8c8d23e$1(GridFinishedFuture.java:180)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$0(GridFinishedFuture.java:163)
> ~[classes/:?]
> {code}
> 2) Even we fix the cast, another failure may arise. If cache with node filter
> was created by a client or not by the excluded node (or may be not from the
> coordinator), the dump content may be checked before anything is written.
> {code:java}
> Caused by: class org.apache.ignite.IgniteException: Ouch! Argument is
> invalid: binary metadata directory not exists
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsVerifyHandler.checkDumpFiles(SnapshotPartitionsVerifyHandler.java:382)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsVerifyHandler.invoke(SnapshotPartitionsVerifyHandler.java:183)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsQuickVerifyHandler.invoke(SnapshotPartitionsQuickVerifyHandler.java:62)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsQuickVerifyHandler.invoke(SnapshotPartitionsQuickVerifyHandler.java:37)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.invoke(IgniteSnapshotManager.java:3396)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.lambda$invokeAll$8d56ceed$1(IgniteSnapshotManager.java:3328)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11715)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11617)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11597)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.invokeAll(IgniteSnapshotManager.java:3325)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.lambda$initLocalFullSnapshot$923db49$1(IgniteSnapshotManager.java:1254)
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$d8c8d23e$1(GridFinishedFuture.java:180)
> at
>
[jira] [Assigned] (IGNITE-21257) Public Java API to get global partition states
[ https://issues.apache.org/jira/browse/IGNITE-21257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-21257: -- Assignee: Ivan Bessonov > Public Java API to get global partition states > -- > > Key: IGNITE-21257 > URL: https://issues.apache.org/jira/browse/IGNITE-21257 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > Please refer to https://issues.apache.org/jira/browse/IGNITE-21140 for the > list. > We should use local partition states, implemented in IGNITE-21256, and > combine them in cluster-wide compute call, before returning to the user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21656) Cache dump fails on a cache with a node filter.
[
https://issues.apache.org/jira/browse/IGNITE-21656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin reassigned IGNITE-21656:
-
Assignee: Vladimir Steshin
> Cache dump fails on a cache with a node filter.
> ---
>
> Key: IGNITE-21656
> URL: https://issues.apache.org/jira/browse/IGNITE-21656
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Ignite may fail to create dump of cache with a node filter.
> 1) If there are no partitions on some node, we assign the empty set as the
> snapshot task result:
> {code:java}
> if (parts.isEmpty() && !withMetaStorage)
> task0 = new GridFinishedFuture<>(Collections.emptySet());
> else {
> ...
> }
> {code}
> Cache dump doesn't contain the metastorage. Further, we may cast the result to
> {code:java}
> SnapshotFutureTaskResult res = (SnapshotFutureTaskResult)task0.result();
> {code}
> but it is a
> {code:java}
> Collections#EMPTY_SET
> {code}
> Stacktrace:
> {code:java}
> [ERROR][snapshot-runner-#413%dump.IgniteCacheDumpSelfTest0%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.lang.ClassCastException: class
> java.util.Collections$EmptySet cannot be cast to class
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> (java.util.Collections$EmptySet is in module java.base of loader 'bootstrap';
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult is in
> unnamed module of loader 'app')]]
> java.lang.ClassCastException: class java.util.Collections$EmptySet cannot be
> cast to class
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> (java.util.Collections$EmptySet is in module java.base of loader
> 'bootstrap';
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> is in unnamed module of loader 'app')
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.lambda$initLocalFullSnapshot$923db49$1(IgniteSnapshotManager.java:1221)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$d8c8d23e$1(GridFinishedFuture.java:180)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$0(GridFinishedFuture.java:163)
> ~[classes/:?]
> {code}
> 2) Even we fix the cast, another failure may arise. If cache with node filter
> was created by a client or not by the excluded node (or may be not from the
> coordinator), the dump content may be checked before anything is written.
> {code:java}
> Caused by: class org.apache.ignite.IgniteException: Ouch! Argument is
> invalid: binary metadata directory not exists
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsVerifyHandler.checkDumpFiles(SnapshotPartitionsVerifyHandler.java:382)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsVerifyHandler.invoke(SnapshotPartitionsVerifyHandler.java:183)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsQuickVerifyHandler.invoke(SnapshotPartitionsQuickVerifyHandler.java:62)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotPartitionsQuickVerifyHandler.invoke(SnapshotPartitionsQuickVerifyHandler.java:37)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.invoke(IgniteSnapshotManager.java:3396)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.lambda$invokeAll$8d56ceed$1(IgniteSnapshotManager.java:3328)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11715)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11617)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:11597)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$SnapshotHandlers.invokeAll(IgniteSnapshotManager.java:3325)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.lambda$initLocalFullSnapshot$923db49$1(IgniteSnapshotManager.java:1254)
> at
> org.apache.ignite.internal.util.future.GridFinishedFuture.lambda$chain$d8c8d23e$1(GridFinishedFuture.java:180)
> at
>
[jira] [Updated] (IGNITE-16262) Remove the hash join index section from docs
[ https://issues.apache.org/jira/browse/IGNITE-16262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16262: - Labels: documentation (was: docuentation documentation) > Remove the hash join index section from docs > > > Key: IGNITE-16262 > URL: https://issues.apache.org/jira/browse/IGNITE-16262 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.11.1 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: documentation > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to remove the hash join index section from the docs > ([https://ignite.apache.org/docs/latest/SQL/distributed-joins#hash-joins]) as > there is no such functionality in Apache Ignite. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21928) Describe Catalog operation flow in README
[ https://issues.apache.org/jira/browse/IGNITE-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21928: Epic Link: IGNITE-21991 (was: IGNITE-21211) > Describe Catalog operation flow in README > - > > Key: IGNITE-21928 > URL: https://issues.apache.org/jira/browse/IGNITE-21928 > Project: Ignite > Issue Type: Improvement >Reporter: Iurii Gerzhedovich >Priority: Major > > Describe CatalogService operations in README.md -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21892) ItPlacementDriverReplicaSideTest testNotificationToPlacementDriverAboutChangeLeader is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-21892:
Assignee: Alexander Lapin
> ItPlacementDriverReplicaSideTest
> testNotificationToPlacementDriverAboutChangeLeader is flaky
>
>
> Key: IGNITE-21892
> URL: https://issues.apache.org/jira/browse/IGNITE-21892
> Project: Ignite
> Issue Type: Bug
>Reporter: Maksim Zhuravkov
>Assignee: Alexander Lapin
>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 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] [Commented] (IGNITE-20628) testDropColumn and testMergeChangesAddDropAdd in ItSchemaChangeKvViewTest are disabled
[ https://issues.apache.org/jira/browse/IGNITE-20628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834245#comment-17834245 ] Denis Chudov commented on IGNITE-20628: --- IGNITE-21572 is resolved, but due to the rare occurrence of this error, we need to monitor the teamcity for some time (about a month). After that, if this error is no longer reproduced, we can close this ticket. > testDropColumn and testMergeChangesAddDropAdd in ItSchemaChangeKvViewTest are > disabled > -- > > Key: IGNITE-20628 > URL: https://issues.apache.org/jira/browse/IGNITE-20628 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-beta2 > > > It was supposed that IGNITE-17931 was the culprit, but even after removing > the blocking code the tests are still flaky. > The tests fail with one of 3 symptoms: > # An NPE happens in the test method code: a value by a key for which a put > is made earlier is not found when using the same key. This is probably caused > by a transactional protocol implementation bug, maybe this: IGNITE-20116 > # A PrimaryReplicaAwaitTimeoutException > # A ReplicationTimeoutException > Items 2 and 3 need to be investigated. > h2. A stacktrace for 1 > java.lang.NullPointerException > at > org.apache.ignite.internal.runner.app.ItSchemaChangeKvViewTest.testDropColumn(ItSchemaChangeKvViewTest.java:58) > h2. A stacktrace for 2 > org.apache.ignite.tx.TransactionException: IGN-PLACEMENTDRIVER-1 > TraceId:0a32c369-b9ca-4091-b8de-af15d65a1f52 Failed to get the primary > replica [tablePartitionId=3_part_5, awaitTimestamp=HybridTimestamp > [time=111220884095959043, physical=1697096009765, logical=3]] > > at > org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:400) > at > org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461) > at > org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:400) > at > org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlist$71(InternalTableImpl.java:1659) > at > java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930) > at > java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907) > at > java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) > at > java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) > at > java.base/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) > 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: java.util.concurrent.CompletionException: > org.apache.ignite.internal.placementdriver.PrimaryReplicaAwaitTimeoutException: > IGN-PLACEMENTDRIVER-1 TraceId:0a32c369-b9ca-4091-b8de-af15d65a1f52 The > primary replica await timed out [replicationGroupId=3_part_5, > referenceTimestamp=HybridTimestamp [time=111220884095959043, > physical=1697096009765, logical=3], currentLease=Lease > [leaseholder=isckvt_tmcada_3346, accepted=false, startTime=HybridTimestamp > [time=111220884127809550, physical=1697096010251, logical=14], > expirationTime=HybridTimestamp [time=111220891992129536, > physical=1697096130251, logical=0], prolongable=false, > replicationGroupId=3_part_5]] > at > java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) > at > java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) > at > java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990) > at > java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970) > ... 9 more > Caused by: > org.apache.ignite.internal.placementdriver.PrimaryReplicaAwaitTimeoutException: > IGN-PLACEMENTDRIVER-1 TraceId:0a32c369-b9ca-4091-b8de-af15d65a1f52 The > primary replica await timed out [replicationGroupId=3_part_5, > referenceTimestamp=HybridTimestamp [time=111220884095959043, > physical=1697096009765, logical=3], currentLease=Lease > [leaseholder=isckvt_tmcada_3346, accepted=false, startTime=HybridTimestamp >
[jira] [Commented] (IGNITE-21418) ItTxDistributedTestThreeNodesThreeReplicas#testDeleteUpsertAllRollback is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834247#comment-17834247
]
Denis Chudov commented on IGNITE-21418:
---
IGNITE-21572 is a possible reason. It is resolved, but due to the rare
occurrence of this error, we need to monitor the teamcity for some time (about
a month). After that, if this error is no longer reproduced, we can close this
ticket.
> ItTxDistributedTestThreeNodesThreeReplicas#testDeleteUpsertAllRollback is
> flaky
> ---
>
> Key: IGNITE-21418
> URL: https://issues.apache.org/jira/browse/IGNITE-21418
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> java.lang.NullPointerException at
> org.apache.ignite.internal.table.TxAbstractTest.testDeleteUpsertAllRollback(TxAbstractTest.java:233)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> {code}
> [https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7814256?expandCode+Inspection=true=true=false=true=false=true]
> Flaky rate is low.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21991) Catalog service Phase 3. Clean up and additional tests
Iurii Gerzhedovich created IGNITE-21991: --- Summary: Catalog service Phase 3. Clean up and additional tests Key: IGNITE-21991 URL: https://issues.apache.org/jira/browse/IGNITE-21991 Project: Ignite Issue Type: Epic Reporter: Iurii Gerzhedovich -- 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 ] Julia Bakulina updated IGNITE-21835: Description: To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS and all MvccUtils classes. was: To delete unused Mvcc code from enum RowData: * LINK_ONLY * LINK_WITH_HEADER * NO_KEY_WTH_HINTS > 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 > and all MvccUtils classes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20912) Ability to switch debug log level for ConflictResolver during runtime
[
https://issues.apache.org/jira/browse/IGNITE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julia Bakulina reassigned IGNITE-20912:
---
Assignee: Julia Bakulina
> Ability to switch debug log level for ConflictResolver during runtime
> -
>
> Key: IGNITE-20912
> URL: https://issues.apache.org/jira/browse/IGNITE-20912
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: IEP-59, ise
>
> Currently, we can not switch debug log level for conflict resolver during
> runtime. There are two conflict resolvers, one of which is chosen in
> {{CacheConflictResolutionManagerImpl}} during cache start. For DEBUG level
> {{DebugCacheVersionConflictResolverImpl}} is used, otherwise
> {{CacheVersionConflictResolverImpl}} is chosen.
> If you enable or disable log debug level for conflict resolver during
> runtime, switching of conflict resolver implementation is not performed and
> you have to restart server node in order to provide necessary log level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21921) Cover SQL E071-1 (Basic query expressions, UNION DISTINCT table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-21921: Ignite Flags: (was: Docs Required,Release Notes Required) > Cover SQL E071-1 (Basic query expressions, UNION DISTINCT table operator) > feature by tests > -- > > Key: IGNITE-21921 > URL: https://issues.apache.org/jira/browse/IGNITE-21921 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E071-1 (Basic query expressions, UNION > DISTINCT table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21619) "Failed to get the primary replica" after massive data insert and node restart
[
https://issues.apache.org/jira/browse/IGNITE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-21619:
Assignee: Alexander Lapin
> "Failed to get the primary replica" after massive data insert and node restart
> --
>
> Key: IGNITE-21619
> URL: https://issues.apache.org/jira/browse/IGNITE-21619
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, sql
> Attachments: ignite-config.conf, ignite3db-0.log
>
>
> Steps to reproduce:
> 1. Start a 1-node cluster.
> 2 Create several tables (5, for example) in aipersist zone.
> 3. Fill these tables with some data (1000 rows each, for example).
> 4. Verify that data is accessible via SQL.
> 5. Restart a node.
> 6. Try to fetch the same data again.
> Expected result: we could fetch data.
> Actual result: data is inaccessible.
> Trace on the client side:
> {code}
> java.sql.SQLException: Failed to get the primary replica
> [tablePartitionId=6_part_1]
> at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:154)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.executeQuery(JdbcStatement.java:111)
>...
> {code}
> Trace in node log (attached):
> {code}
> 2024-02-28 12:36:34:807 +0500
> [INFO][%ClusterFailoverTest_cluster_0%sql-execution-pool-0][JdbcQueryEventHandlerImpl]
> Exception while executing query [query=select sum(k1) from failoverTest00]
> org.apache.ignite.sql.SqlException: IGN-CMN-65535
> TraceId:8d366905-a4bb-4333-b0b3-c647a1cf943f Failed to get the primary
> replica [tablePartitionId=6_part_1]
> at
> org.apache.ignite.internal.lang.SqlExceptionMapperUtil.mapToPublicSqlException(SqlExceptionMapperUtil.java:61)
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.wrapIfNecessary(AsyncSqlCursorImpl.java:180)
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.handleError(AsyncSqlCursorImpl.java:157)
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$2(AsyncSqlCursorImpl.java:96)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl$DistributedQueryManager.lambda$execute$18(ExecutionServiceImpl.java:864)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:83)
> 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:829)
> Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:8d366905-a4bb-4333-b0b3-c647a1cf943f Failed to get the primary
> replica [tablePartitionId=6_part_1]
> at
> org.apache.ignite.internal.lang.IgniteExceptionMapperUtil.mapToPublicException(IgniteExceptionMapperUtil.java:117)
> at
> org.apache.ignite.internal.lang.SqlExceptionMapperUtil.mapToPublicSqlException(SqlExceptionMapperUtil.java:51)
> ... 15 more
> Caused by: org.apache.ignite.internal.lang.IgniteInternalException:
> IGN-PLACEMENTDRIVER-1 TraceId:8d366905-a4bb-4333-b0b3-c647a1cf943f Failed to
> get the primary replica [tablePartitionId=6_part_1]
> at
> org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:384)
> at
> org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:446)
> at
> org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:384)
> at
> org.apache.ignite.internal.sql.engine.SqlQueryProcessor.lambda$primaryReplicas$2(SqlQueryProcessor.java:402)
> at
>
[jira] [Commented] (IGNITE-21656) Cache dump fails on a cache with a node filter.
[
https://issues.apache.org/jira/browse/IGNITE-21656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834234#comment-17834234
]
Ignite TC Bot commented on IGNITE-21656:
{panel:title=Branch: [pull/11276/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11276/head] Base: [master] : New Tests
(24)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Snapshots 3{color} [[tests
24|https://ci2.ignite.apache.org/viewLog.html?buildId=7812498]]
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=true,mode=TRANSACTIONAL,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=true,mode=TRANSACTIONAL,useDataStreamer=false,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=false,mode=TRANSACTIONAL,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=false,mode=TRANSACTIONAL,useDataStreamer=false,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=true,mode=ATOMIC,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=true,mode=ATOMIC,useDataStreamer=false,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=1,persistence=true,mode=TRANSACTIONAL,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=1,persistence=true,mode=TRANSACTIONAL,useDataStreamer=true,onlyPrimary=true,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=false,mode=ATOMIC,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=0,persistence=false,mode=ATOMIC,useDataStreamer=false,onlyPrimary=false,encrypted=false]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite3:
IgniteCacheDumpSelfTest.testDumpWithNodeFilterCache[nodes=3,backups=1,persistence=true,mode=ATOMIC,useDataStreamer=true,onlyPrimary=false,encrypted=false]
- PASSED{color}
... and 13 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7812499buildTypeId=IgniteTests24Java8_RunAll]
> Cache dump fails on a cache with a node filter.
> ---
>
> Key: IGNITE-21656
> URL: https://issues.apache.org/jira/browse/IGNITE-21656
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Ignite may fail to create dump of cache with a node filter.
> 1) If there are no partitions on some node, we assign the empty set as the
> snapshot task result:
> {code:java}
> if (parts.isEmpty() && !withMetaStorage)
> task0 = new GridFinishedFuture<>(Collections.emptySet());
> else {
> ...
> }
> {code}
> Cache dump doesn't contain the metastorage. Further, we may cast the result to
> {code:java}
> SnapshotFutureTaskResult res = (SnapshotFutureTaskResult)task0.result();
> {code}
> but it is a
> {code:java}
> Collections#EMPTY_SET
> {code}
> Stacktrace:
> {code:java}
> [ERROR][snapshot-runner-#413%dump.IgniteCacheDumpSelfTest0%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.lang.ClassCastException: class
> java.util.Collections$EmptySet cannot be cast to class
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
> (java.util.Collections$EmptySet is in module java.base of loader 'bootstrap';
> o.a.i.i.processors.cache.persistence.snapshot.SnapshotFutureTaskResult
[jira] [Updated] (IGNITE-21494) Data Streamer: use one shared executor per node for flushTimer
[ https://issues.apache.org/jira/browse/IGNITE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21494: Description: Currently, every *StreamerSubscriber* instance creates a new *SingleThreadScheduledExecutor* for the *flushTimer*, which means a new thread for every streamer. This is excessive. One executor per node or client should be enough. was: Currently, every *StreamSubscriber* instance creates a new *SingleThreadScheduledExecutor* for the *flushTimer*, which means a new thread for every streamer. This is excessive. One executor per node or client should be enough. > Data Streamer: use one shared executor per node for flushTimer > -- > > Key: IGNITE-21494 > URL: https://issues.apache.org/jira/browse/IGNITE-21494 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Currently, every *StreamerSubscriber* instance creates a new > *SingleThreadScheduledExecutor* for the *flushTimer*, which means a new > thread for every streamer. > This is excessive. One executor per node or client should be enough. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21988) Don't allow reading from index storage if it is in build state
[ https://issues.apache.org/jira/browse/IGNITE-21988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834224#comment-17834224 ] Roman Puchkovskiy commented on IGNITE-21988: The patch looks good to me > Don't allow reading from index storage if it is in build state > -- > > Key: IGNITE-21988 > URL: https://issues.apache.org/jira/browse/IGNITE-21988 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to prohibit read operations from > *org.apache.ignite.internal.storage.index.IndexStorage* if they are in build > state. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21929) Skip pending list extra cleanup in TTL Manager
[ https://issues.apache.org/jira/browse/IGNITE-21929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov resolved IGNITE-21929. Release Note: Fixed pending tree redundant cleanup on entries expiration Resolution: Fixed [~yuri.naryshkin], looks good to me. Merged to master. Thanks for the contribution! > Skip pending list extra cleanup in TTL Manager > -- > > Key: IGNITE-21929 > URL: https://issues.apache.org/jira/browse/IGNITE-21929 > Project: Ignite > Issue Type: Improvement >Reporter: Yuri Naryshkin >Assignee: Yuri Naryshkin >Priority: Major > Labels: ise > Fix For: 2.17 > > Time Spent: 50m > Remaining Estimate: 0h > > Currently when records expire with high rate, several threads (sys-stripe, > client-connector) try to cleanup those records and get stuck waiting to > acquire lock on main page of PendingEntriesTree. This is unnecessary > contention. > After introducing fix for IGNITE-14341 expired records PendingEntriesTree > cleanup is done using range. After that each record is deleted from dataTree. > And after that another attempt is done to remove each record from > PendingEntriesTree once again, which is not necessary as the record is > already removed. > This ticket is to improve cleaning up expired entries by skipping second > attempt to remove each record from PendingEntriesTree. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21906) Consider disabling inline in PK index by default
[ https://issues.apache.org/jira/browse/IGNITE-21906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev reassigned IGNITE-21906: Assignee: Aleksandr Polovtcev > Consider disabling inline in PK index by default > > > Key: IGNITE-21906 > URL: https://issues.apache.org/jira/browse/IGNITE-21906 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > > In aipersist/aimem we attempt to inline binary tuples into pages for hash > indexes by default. This, in theory, saves us from the necessity of accessing > binary tuples from data pages for comparison, which is slower than comparing > inlined data. > But, assuming the good hash distribution, we would only have to do the real > comparison for the matched tuple. At the same time, inlined data might be > substantially larger than hash+link, meaning that B+Tree with inlined data > has bigger height, which correlates with slower search speed. > So, we have both pros and cons for inlining, and the only real way to > reconcile them is to compare them with some benchmarks. This is exactly what > I propose. > TL;DR: force inline size to be 0 for hash indices and benchmark for put/get > operations, with large enough amount of data. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21995) Do not disable thread assertions in tests
Roman Puchkovskiy created IGNITE-21995: -- Summary: Do not disable thread assertions in tests Key: IGNITE-21995 URL: https://issues.apache.org/jira/browse/IGNITE-21995 Project: Ignite Issue Type: Improvement Reporter: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21773) Don't notify low watermark update listeners at node start
[ https://issues.apache.org/jira/browse/IGNITE-21773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-21773: - Fix Version/s: 3.0.0-beta2 > Don't notify low watermark update listeners at node start > - > > Key: IGNITE-21773 > URL: https://issues.apache.org/jira/browse/IGNITE-21773 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 2h > Remaining Estimate: 0h > > I noticed that at the moment we are notifying listeners on the start node > about updating the low watermark, although this is not necessary and each > component can read the latest watermark at the start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21919) Cover SQL E031-3 (Identifiers, Trailing underscore feature) by tests
[ https://issues.apache.org/jira/browse/IGNITE-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-21919: - Assignee: Pavel Pereslegin > Cover SQL E031-3 (Identifiers, Trailing underscore feature) by tests > > > Key: IGNITE-21919 > URL: https://issues.apache.org/jira/browse/IGNITE-21919 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E031-3 (Identifiers, Trailing underscore > feature) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21916) Cover SQL T828 (JSON_QUERY) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-21916: - Assignee: Pavel Pereslegin > Cover SQL T828 (JSON_QUERY) feature by tests > > > Key: IGNITE-21916 > URL: https://issues.apache.org/jira/browse/IGNITE-21916 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for T828 (JSON_QUERY) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21919) Cover SQL E031-3 (Identifiers, Trailing underscore feature) by tests
[ https://issues.apache.org/jira/browse/IGNITE-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-21919: - Assignee: (was: Pavel Pereslegin) > Cover SQL E031-3 (Identifiers, Trailing underscore feature) by tests > > > Key: IGNITE-21919 > URL: https://issues.apache.org/jira/browse/IGNITE-21919 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E031-3 (Identifiers, Trailing underscore > feature) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834359#comment-17834359 ] Chris Dennis commented on IGNITE-13114: --- I did, I mentioned you 4 years ago when I originally created the PR ;) > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21922) Cover SQL E141-01(Basic integrity constraints, NOT NULL constraints) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21922: Summary: Cover SQL E141-01(Basic integrity constraints, NOT NULL constraints) feature by tests (was: Cover SQL E141-1(Basic integrity constraints, NOT NULL constraints) feature by tests) > Cover SQL E141-01(Basic integrity constraints, NOT NULL constraints) feature > by tests > - > > Key: IGNITE-21922 > URL: https://issues.apache.org/jira/browse/IGNITE-21922 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E141-1(Basic integrity constraints, NOT > NULL constraints) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21997) Expose dump creating status into snapshot metrics
Yuri Naryshkin created IGNITE-21997: --- Summary: Expose dump creating status into snapshot metrics Key: IGNITE-21997 URL: https://issues.apache.org/jira/browse/IGNITE-21997 Project: Ignite Issue Type: Task Reporter: Yuri Naryshkin Assignee: Yuri Naryshkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21997) Expose dump creating status into snapshot metrics
[ https://issues.apache.org/jira/browse/IGNITE-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri Naryshkin updated IGNITE-21997: Labels: ise (was: ) > Expose dump creating status into snapshot metrics > - > > Key: IGNITE-21997 > URL: https://issues.apache.org/jira/browse/IGNITE-21997 > Project: Ignite > Issue Type: Task >Reporter: Yuri Naryshkin >Assignee: Yuri Naryshkin >Priority: Major > Labels: ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-19274) Sql. Jdbc client. Support TIMESTAMP WITH LOCAL TIME ZONE type
[ https://issues.apache.org/jira/browse/IGNITE-19274 ]
Pavel Pereslegin deleted comment on IGNITE-19274:
---
was (Author: xtern):
If we continue to convert {{Timestamp}} to {{LocalDateTime}}, we may have to
rework the {{Instant}} to {{Timestamp}} conversion when reading the result set.
Something like this:
{code:java}
if (cls == Instant.class) {
return Timestamp.valueOf(LocalDateTime.ofInstant((Instant) val,
ZoneId.of("UTC")));
{code}
> Sql. Jdbc client. Support TIMESTAMP WITH LOCAL TIME ZONE type
> --
>
> Key: IGNITE-19274
> URL: https://issues.apache.org/jira/browse/IGNITE-19274
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{TIMESTAMP WITH LOCAL TIME ZONE}} data type is a variant of
> {{TIMESTAMP}} that includes a time zone offset in its value. Data stored in
> the database is normalized to the database time zone (UTC) and time zone
> offset is not stored as part of the column data. When the data is retrieved,
> it to be returned in the user's local session time zone.
> i.e:
> {noformat}
> CREATE TABLE timestamp(ts TIMESTAMP, t_tz TIMESTAMP WITH LOCAL TIME ZONE);
> SET TIME ZONE 'tz1';
> INSERT INTO timestamp VALUES ('2011-01-01 01:01:01', TIMESTAMP WITH LOCAL
> TIME ZONE '2011-01-01 01:01:01');
> SET TIME ZONE 'tz2';
> INSERT INTO timestamp VALUES ('2011-01-01 01:01:01', TIMESTAMP WITH LOCAL
> TIME ZONE '2011-01-01 01:01:01');
> ...
> select * from timestamp;{noformat}
> returned rows need to be different in case of different tz1 and tz2 offsets
> but they are equals for now. Also returned representation need to be present
> in user session time zone.
> h5. Update from 26.02.2024:
> Definition of done for this task:
> * Client time zone is passed to server (check other database implementations
> to decide how and when to pass it).
> * Data of type "TIMESTAMP With LOCAL TIME ZONE" can be written/read correctly
> using the dynamic parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21993) Move WAL sync under if statement
Philipp Shergalis created IGNITE-21993: -- Summary: Move WAL sync under if statement Key: IGNITE-21993 URL: https://issues.apache.org/jira/browse/IGNITE-21993 Project: Ignite Issue Type: Bug Reporter: Philipp Shergalis Assignee: Philipp Shergalis Currently log is synced every time onFlushBegin is called -> multiple times for one flush if there are multiple column families https://github.com/apache/ignite-3/blob/main/modules/rocksdb-common/src/main/java/org/apache/ignite/internal/rocksdb/flush/RocksDbFlushListener.java#L73 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-21916) Cover SQL T828 (JSON_QUERY) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21916 ] Pavel Pereslegin deleted comment on IGNITE-21916: --- was (Author: xtern): We actually have a test called "testJson". The test is muted with IGNITE-20163 issue. > Cover SQL T828 (JSON_QUERY) feature by tests > > > Key: IGNITE-21916 > URL: https://issues.apache.org/jira/browse/IGNITE-21916 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for T828 (JSON_QUERY) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21921) Cover SQL E071-01 (Basic query expressions, UNION DISTINCT table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21921: Summary: Cover SQL E071-01 (Basic query expressions, UNION DISTINCT table operator) feature by tests (was: Cover SQL E071-1 (Basic query expressions, UNION DISTINCT table operator) feature by tests) > Cover SQL E071-01 (Basic query expressions, UNION DISTINCT table operator) > feature by tests > --- > > Key: IGNITE-21921 > URL: https://issues.apache.org/jira/browse/IGNITE-21921 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We don't have at all any tests for E071-1 (Basic query expressions, UNION > DISTINCT table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21919) Cover SQL E031-03 (Identifiers, Trailing underscore feature) by tests
[ https://issues.apache.org/jira/browse/IGNITE-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21919: Summary: Cover SQL E031-03 (Identifiers, Trailing underscore feature) by tests (was: Cover SQL E031-3 (Identifiers, Trailing underscore feature) by tests) > Cover SQL E031-03 (Identifiers, Trailing underscore feature) by tests > - > > Key: IGNITE-21919 > URL: https://issues.apache.org/jira/browse/IGNITE-21919 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E031-3 (Identifiers, Trailing underscore > feature) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21919) Cover SQL E031-03 (Identifiers, Trailing underscore feature) by tests
[ https://issues.apache.org/jira/browse/IGNITE-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21919: Description: We don't have at all any tests for E031-03 (Identifiers, Trailing underscore feature) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to covered area was: We don't have at all any tests for E031-3 (Identifiers, Trailing underscore feature) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to covered area > Cover SQL E031-03 (Identifiers, Trailing underscore feature) by tests > - > > Key: IGNITE-21919 > URL: https://issues.apache.org/jira/browse/IGNITE-21919 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E031-03 (Identifiers, Trailing underscore > feature) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21920) Cover SQL E051-04 (Basic query specification, GROUP BY can contain columns not in ) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21920: Summary: Cover SQL E051-04 (Basic query specification, GROUP BY can contain columns not in ) feature by tests (was: Cover SQL E051-4 (Basic query specification, GROUP BY can contain columns not in ) feature by tests) > Cover SQL E051-04 (Basic query specification, GROUP BY can contain columns > not in ) feature by tests > - > > Key: IGNITE-21920 > URL: https://issues.apache.org/jira/browse/IGNITE-21920 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E051-4 (Basic query specification, GROUP > BY can contain columns not in ) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20606) Add support "ALTER ZONE SET DEFAULT" syntax to reassign default zone.
[
https://issues.apache.org/jira/browse/IGNITE-20606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-20606:
-
Assignee: Pavel Pereslegin
> Add support "ALTER ZONE SET DEFAULT" syntax to reassign default
> zone.
> -
>
> Key: IGNITE-20606
> URL: https://issues.apache.org/jira/browse/IGNITE-20606
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> We need to add SQL syntax to support setting a default zone.
> Also this command must be converted to a catalog command
> h3. *Definition of done*
> Corresponding command must be added:
> * {{ALTER ZONE SET DEFAULT}} to reassign default zone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21996) Sql. SET DATA TYPE command allow change from not null to null
[
https://issues.apache.org/jira/browse/IGNITE-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-21996:
Summary: Sql. SET DATA TYPE command allow change from not null to null
(was: SET DATA TYPE command allow change from not null to null)
> Sql. SET DATA TYPE command allow change from not null to null
> -
>
> Key: IGNITE-21996
> URL: https://issues.apache.org/jira/browse/IGNITE-21996
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> As of now absent validation during the amend column from NOT NULLABLE to
> NULLABLE in case using DDL command
> {code:java}
> ALTER TABLE ... ALTER COLUMN ... SET DATA TYPE NOT NULL ...{code}
>
> Let's fix it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21996) SET DATA TYPE command allow change from not null to null
Iurii Gerzhedovich created IGNITE-21996:
---
Summary: SET DATA TYPE command allow change from not null to null
Key: IGNITE-21996
URL: https://issues.apache.org/jira/browse/IGNITE-21996
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Iurii Gerzhedovich
As of now absent validation during the amend column from NOT NULLABLE to
NULLABLE in case using DDL command
{code:java}
ALTER TABLE ... ALTER COLUMN ... SET DATA TYPE NOT NULL ...{code}
Let's fix it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834354#comment-17834354 ] Anton Vinogradov commented on IGNITE-13114: --- [~chrisdennis], sure, don't forget to mention someone nextime to be seen :) > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21922) Cover SQL E141-01(Basic integrity constraints, NOT NULL constraints) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21922: Description: We don't have at all any tests for E141-01(Basic integrity constraints, NOT NULL constraints) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for E141-1(Basic integrity constraints, NOT NULL constraints) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL E141-01(Basic integrity constraints, NOT NULL constraints) feature > by tests > - > > Key: IGNITE-21922 > URL: https://issues.apache.org/jira/browse/IGNITE-21922 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E141-01(Basic integrity constraints, NOT > NULL constraints) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21939) Cover SQL F302-02(INTERSECT table operator. INTERSECT ALL table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21939: Description: We don't have at all any tests for F302-02(INTERSECT table operator. INTERSECT ALL table operator) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for F302-2(INTERSECT table operator. INTERSECT ALL table operator) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL F302-02(INTERSECT table operator. INTERSECT ALL table operator) > feature by tests > -- > > Key: IGNITE-21939 > URL: https://issues.apache.org/jira/browse/IGNITE-21939 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F302-02(INTERSECT table operator. > INTERSECT ALL table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21939) Cover SQL F302-02(INTERSECT table operator. INTERSECT ALL table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21939: Summary: Cover SQL F302-02(INTERSECT table operator. INTERSECT ALL table operator) feature by tests (was: Cover SQL F302-2(INTERSECT table operator. INTERSECT ALL table operator) feature by tests) > Cover SQL F302-02(INTERSECT table operator. INTERSECT ALL table operator) > feature by tests > -- > > Key: IGNITE-21939 > URL: https://issues.apache.org/jira/browse/IGNITE-21939 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F302-2(INTERSECT table operator. INTERSECT > ALL table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21920) Cover SQL E051-04 (Basic query specification, GROUP BY can contain columns not in ) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21920: Description: We don't have at all any tests for E051-04 (Basic query specification, GROUP BY can contain columns not in ) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to covered area was: We don't have at all any tests for E051-4 (Basic query specification, GROUP BY can contain columns not in ) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to covered area > Cover SQL E051-04 (Basic query specification, GROUP BY can contain columns > not in ) feature by tests > - > > Key: IGNITE-21920 > URL: https://issues.apache.org/jira/browse/IGNITE-21920 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E051-04 (Basic query specification, GROUP > BY can contain columns not in ) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834301#comment-17834301 ] Chris Dennis commented on IGNITE-13114: --- Rebased this again today. Anyone care to merge a trivial fix to a decade old, obvious off-by-one bug? > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21751) LowWatermark implementation refactoring.
[ https://issues.apache.org/jira/browse/IGNITE-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko resolved IGNITE-21751. -- Resolution: Duplicate > LowWatermark implementation refactoring. > > > Key: IGNITE-21751 > URL: https://issues.apache.org/jira/browse/IGNITE-21751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > LWM stats before any other it's dependant component. > So, there is no need to notify listeners on start, because no one subscribed > yet. > There is no need to notify TxManager on start, TxManager can just ask for the > current LWM directly. > Also, it would be nice to have an option triggering LWM update forcibly. > E.g for test purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21916) Cover SQL T828 (JSON_QUERY) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834333#comment-17834333 ] Pavel Pereslegin commented on IGNITE-21916: --- We actually have a test called "testJson". The test is muted with IGNITE-20163 issue. > Cover SQL T828 (JSON_QUERY) feature by tests > > > Key: IGNITE-21916 > URL: https://issues.apache.org/jira/browse/IGNITE-21916 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for T828 (JSON_QUERY) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21937) Cover SQL F041-05(Basic joined table. Outer joins can be nested) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21937: Description: We don't have at all any tests for F041-05(Basic joined table. Outer joins can be nested) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for F041-5(Basic joined table. Outer joins can be nested) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL F041-05(Basic joined table. Outer joins can be nested) feature by > tests > - > > Key: IGNITE-21937 > URL: https://issues.apache.org/jira/browse/IGNITE-21937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F041-05(Basic joined table. Outer joins > can be nested) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21937) Cover SQL F041-05(Basic joined table. Outer joins can be nested) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21937: Summary: Cover SQL F041-05(Basic joined table. Outer joins can be nested) feature by tests (was: Cover SQL F041-50(Basic joined table. Outer joins can be nested) feature by tests) > Cover SQL F041-05(Basic joined table. Outer joins can be nested) feature by > tests > - > > Key: IGNITE-21937 > URL: https://issues.apache.org/jira/browse/IGNITE-21937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F041-5(Basic joined table. Outer joins can > be nested) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21937) Cover SQL F041-50(Basic joined table. Outer joins can be nested) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21937: Summary: Cover SQL F041-50(Basic joined table. Outer joins can be nested) feature by tests (was: Cover SQL F041-5(Basic joined table. Outer joins can be nested) feature by tests) > Cover SQL F041-50(Basic joined table. Outer joins can be nested) feature by > tests > - > > Key: IGNITE-21937 > URL: https://issues.apache.org/jira/browse/IGNITE-21937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F041-5(Basic joined table. Outer joins can > be nested) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21938) Cover SQL F041-07(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21938: Summary: Cover SQL F041-07(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) feature by tests (was: Cover SQL F041-7(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) feature by tests) > Cover SQL F041-07(Basic joined table. The inner table in a left or right > outer join can also be used in an inner join) feature by tests > --- > > Key: IGNITE-21938 > URL: https://issues.apache.org/jira/browse/IGNITE-21938 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F041-7(Basic joined table. The inner table > in a left or right outer join can also be used in an inner join) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21938) Cover SQL F041-07(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21938: Description: We don't have at all any tests for F041-07(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for F041-7(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL F041-07(Basic joined table. The inner table in a left or right > outer join can also be used in an inner join) feature by tests > --- > > Key: IGNITE-21938 > URL: https://issues.apache.org/jira/browse/IGNITE-21938 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F041-07(Basic joined table. The inner > table in a left or right outer join can also be used in an inner join) SQL > feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21921) Cover SQL E071-01 (Basic query expressions, UNION DISTINCT table operator) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21921: Description: We don't have at all any tests for E071-01 (Basic query expressions, UNION DISTINCT table operator) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for E071-1 (Basic query expressions, UNION DISTINCT table operator) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL E071-01 (Basic query expressions, UNION DISTINCT table operator) > feature by tests > --- > > Key: IGNITE-21921 > URL: https://issues.apache.org/jira/browse/IGNITE-21921 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We don't have at all any tests for E071-01 (Basic query expressions, UNION > DISTINCT table operator) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21923) Cover SQL E051-09(Basic query specification, Rename columns in the FROM clause) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21923: Summary: Cover SQL E051-09(Basic query specification, Rename columns in the FROM clause) feature by tests (was: Cover SQL E051-9(Basic query specification, Rename columns in the FROM clause) feature by tests) > Cover SQL E051-09(Basic query specification, Rename columns in the FROM > clause) feature by tests > > > Key: IGNITE-21923 > URL: https://issues.apache.org/jira/browse/IGNITE-21923 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E051-9(Basic query specification, Rename > columns in the FROM clause) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21923) Cover SQL E051-09(Basic query specification, Rename columns in the FROM clause) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21923: Description: We don't have at all any tests for E051-09(Basic query specification, Rename columns in the FROM clause) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area was: We don't have at all any tests for E051-9(Basic query specification, Rename columns in the FROM clause) SQL feature. Let's cover it and create tickets to fix them in case find any issues related to the covered area > Cover SQL E051-09(Basic query specification, Rename columns in the FROM > clause) feature by tests > > > Key: IGNITE-21923 > URL: https://issues.apache.org/jira/browse/IGNITE-21923 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for E051-09(Basic query specification, Rename > columns in the FROM clause) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21994) Broken link to Monitoring Rebalancing Process
Vyacheslav Koptilin created IGNITE-21994: Summary: Broken link to Monitoring Rebalancing Process Key: IGNITE-21994 URL: https://issues.apache.org/jira/browse/IGNITE-21994 Project: Ignite Issue Type: Bug Components: documentation Reporter: Vyacheslav Koptilin The following documentation topic [Monitoring Rebalancing Process|http://https://ignite.apache.org/docs/latest/data-rebalancing#monitoring-rebalancing-process] contains an incorrect link that leads to a non-existent page: [https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-rebalancing] (perhaps this page was moved or deleted). I think we can use [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#caches] where the rebalance metrics are described. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21906) Consider disabling inline in PK index by default
[ https://issues.apache.org/jira/browse/IGNITE-21906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834334#comment-17834334 ] Aleksandr Polovtcev commented on IGNITE-21906: -- I've set the inline size to 0 in all HashIndexTrees and got the following results running YCSB KV scenario: Baseline: [OVERALL] RunTime(ms): 40648 Throughput(ops/sec): 6150.364101554812 Operations(payload): 25 Operations(warm-up): 5 [READ] Operations: 25 AverageLatency(us): 152.338772 MinLatency(us): 125 MaxLatency(us): 16355 95thPercentileLatency(us): 179 99thPercentileLatency(us): 232 Return=OK: 25 No inlining [OVERALL] RunTime(ms): 41874 Throughput(ops/sec): 5970.291827864546 Operations(payload): 25 Operations(warm-up): 5 [READ] Operations: 25 AverageLatency(us): 158.05806 MinLatency(us): 126 MaxLatency(us): 23661 95thPercentileLatency(us): 186 99thPercentileLatency(us): 245 Return=OK: 25 Looks like everything got a little bit slower. > Consider disabling inline in PK index by default > > > Key: IGNITE-21906 > URL: https://issues.apache.org/jira/browse/IGNITE-21906 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > In aipersist/aimem we attempt to inline binary tuples into pages for hash > indexes by default. This, in theory, saves us from the necessity of accessing > binary tuples from data pages for comparison, which is slower than comparing > inlined data. > But, assuming the good hash distribution, we would only have to do the real > comparison for the matched tuple. At the same time, inlined data might be > substantially larger than hash+link, meaning that B+Tree with inlined data > has bigger height, which correlates with slower search speed. > So, we have both pros and cons for inlining, and the only real way to > reconcile them is to compare them with some benchmarks. This is exactly what > I propose. > TL;DR: force inline size to be 0 for hash indices and benchmark for put/get > operations, with large enough amount of data. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21964) Extend test coverage for SQL E031-01(Identifiers. Delimited identifiers)
[ https://issues.apache.org/jira/browse/IGNITE-21964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21964: Description: Test coverage for SQL E031-01(Identifiers. Delimited identifiers) is poor. Let's increase the test coverage. was: Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. Let's increase the test coverage. > Extend test coverage for SQL E031-01(Identifiers. Delimited identifiers) > > > Key: IGNITE-21964 > URL: https://issues.apache.org/jira/browse/IGNITE-21964 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E031-01(Identifiers. Delimited identifiers) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21964) Extend test coverage for SQL E031-01(Identifiers. Delimited identifiers)
[ https://issues.apache.org/jira/browse/IGNITE-21964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-21964: Summary: Extend test coverage for SQL E031-01(Identifiers. Delimited identifiers) (was: Extend test coverage for SQL E031-1(Identifiers. Delimited identifiers)) > Extend test coverage for SQL E031-01(Identifiers. Delimited identifiers) > > > Key: IGNITE-21964 > URL: https://issues.apache.org/jira/browse/IGNITE-21964 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Test coverage for SQL E031-1(Identifiers. Delimited identifiers) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834394#comment-17834394 ] Anton Vinogradov commented on IGNITE-13114: --- And you got your answer each time you mentioned someone ;) > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21490) .NET: Thin 3.0: DataStreamer data removal
[ https://issues.apache.org/jira/browse/IGNITE-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834389#comment-17834389 ] Igor Sapego commented on IGNITE-21490: -- Looks good to me > .NET: Thin 3.0: DataStreamer data removal > - > > Key: IGNITE-21490 > URL: https://issues.apache.org/jira/browse/IGNITE-21490 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement data removal in .NET data streamer - see Java API changes in > IGNITE-21403. -- This message was sent by Atlassian Jira (v8.20.10#820010)
