[jira] [Created] (IGNITE-20690) Ignite client nodes are getting terminated when we stop the ignite server.

Vaibhav Shrivastava created IGNITE-20690: Summary: Ignite client nodes are getting terminated when we stop the ignite server. Key: IGNITE-20690 URL: https://issues.apache.org/jira/browse/IGNITE-20690

[jira] [Commented] (IGNITE-20250) Apache.Ignite.Core.Cluster.IClusterNode.IsDaemon is not accessible anymore in Ignite version of 2.15.0

[ https://issues.apache.org/jira/browse/IGNITE-20250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1016#comment-1016 ] Vaibhav Shrivastava commented on IGNITE-20250: -- Hello [~slava.koptilin] We have modified

[jira] [Created] (IGNITE-20689) [ducktests] Fix a flaky perf_stat_test

Sergey Korotkov created IGNITE-20689: Summary: [ducktests] Fix a flaky perf_stat_test Key: IGNITE-20689 URL: https://issues.apache.org/jira/browse/IGNITE-20689 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-20688) Java Thin Client - Error while deserializing Collection

Rahul Mohan created IGNITE-20688: Summary: Java Thin Client - Error while deserializing Collection Key: IGNITE-20688 URL: https://issues.apache.org/jira/browse/IGNITE-20688 Project: Ignite

[jira] [Commented] (IGNITE-20679) org.apache.ignite.jdbc.thin.JdbcThinCacheToJdbcDataTypesCoverageTest#testSQLTimestampDataType doesn't work on jdk 11 and later

[ https://issues.apache.org/jira/browse/IGNITE-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776899#comment-17776899 ] Ignite TC Bot commented on IGNITE-20679: {panel:title=Branch: [pull/11000/head] Base: [master]

[jira] [Created] (IGNITE-20687) Exclude IgniteTransactions from SQL session creation API

Vladislav Pyatkov created IGNITE-20687: -- Summary: Exclude IgniteTransactions from SQL session creation API Key: IGNITE-20687 URL: https://issues.apache.org/jira/browse/IGNITE-20687 Project:

[jira] [Updated] (IGNITE-20685) Implement initiateRecovery logic

[ https://issues.apache.org/jira/browse/IGNITE-20685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20685: - Description: h3. Motivation Let's assume that somehow dataNode > Implement

[jira] [Created] (IGNITE-20686) Move schema validation on commit to TxManagerImpl

Roman Puchkovskiy created IGNITE-20686: -- Summary: Move schema validation on commit to TxManagerImpl Key: IGNITE-20686 URL: https://issues.apache.org/jira/browse/IGNITE-20686 Project: Ignite

[jira] [Updated] (IGNITE-20598) Java Thin 3.0: incorrect error for query on closed transaction through Client API

[ https://issues.apache.org/jira/browse/IGNITE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20598: Fix Version/s: 3.0.0-beta2 > Java Thin 3.0: incorrect error for query on closed

[jira] [Updated] (IGNITE-20598) Java Thin 3.0: incorrect error for query on closed transaction through Client API

[ https://issues.apache.org/jira/browse/IGNITE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20598: Component/s: thin client > Java Thin 3.0: incorrect error for query on closed

[jira] [Updated] (IGNITE-20598) Java Thin 3.0: incorrect error for query on closed transaction through Client API

[ https://issues.apache.org/jira/browse/IGNITE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20598: Issue Type: Bug (was: Improvement) > Java Thin 3.0: incorrect error for query on closed

[jira] [Assigned] (IGNITE-20598) Java Thin 3.0: incorrect error for query on closed transaction through Client API

[ https://issues.apache.org/jira/browse/IGNITE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-20598: --- Assignee: Pavel Tupitsyn > Java Thin 3.0: incorrect error for query on closed

[jira] [Updated] (IGNITE-20598) Java Thin 3.0: incorrect error for query on closed transaction through Client API

[ https://issues.apache.org/jira/browse/IGNITE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20598: Summary: Java Thin 3.0: incorrect error for query on closed transaction through Client

[jira] [Updated] (IGNITE-20685) Implement initiateRecovery logic

[ https://issues.apache.org/jira/browse/IGNITE-20685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20685: - Epic Link: IGNITE-20007 > Implement initiateRecovery logic >

[jira] [Created] (IGNITE-20685) Implement initiateRecovery logic

Alexander Lapin created IGNITE-20685: Summary: Implement initiateRecovery logic Key: IGNITE-20685 URL: https://issues.apache.org/jira/browse/IGNITE-20685 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-20685) Implement initiateRecovery logic

[ https://issues.apache.org/jira/browse/IGNITE-20685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20685: - Ignite Flags: (was: Docs Required,Release Notes Required) > Implement

[jira] [Comment Edited] (IGNITE-20677) Sql. Improve error reporting in assertThrowsSqlException.

[ https://issues.apache.org/jira/browse/IGNITE-20677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776686#comment-17776686 ] Pavel Pereslegin edited comment on IGNITE-20677 at 10/18/23 1:43 PM:

[jira] [Updated] (IGNITE-20395) Clean up write intents for RW transaction on primary

[ https://issues.apache.org/jira/browse/IGNITE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-20395: - Description: If a transaction was committed/aborted, but for any reason the

[jira] [Created] (IGNITE-20684) Use proper sync method

Vadim Pakhnushev created IGNITE-20684: - Summary: Use proper sync method Key: IGNITE-20684 URL: https://issues.apache.org/jira/browse/IGNITE-20684 Project: Ignite Issue Type: Bug

[jira] [Resolved] (IGNITE-11970) Excessive use of memory in continuous queries

[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov resolved IGNITE-11970. - Resolution: Fixed > Excessive use of memory in continuous queries >

[jira] [Updated] (IGNITE-11970) Excessive use of memory in continuous queries

[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-11970: Fix Version/s: 2.16 > Excessive use of memory in continuous queries >

[jira] [Updated] (IGNITE-20683) "Failed to stop replica" caused by node is stopping

[ https://issues.apache.org/jira/browse/IGNITE-20683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-20683: -- Attachment: ItSqlExamplesTest.java > "Failed to stop replica" caused by node is

[jira] [Commented] (IGNITE-11970) Excessive use of memory in continuous queries

[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776661#comment-17776661 ] Mikhail Petrov commented on IGNITE-11970: - [~alex_pl] Thank you for the review. > Excessive

[jira] [Updated] (IGNITE-20683) "Failed to stop replica" caused by node is stopping

[ https://issues.apache.org/jira/browse/IGNITE-20683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-20683: -- Attachment: IGNITE-20683.txt > "Failed to stop replica" caused by node is stopping >

[jira] [Created] (IGNITE-20683) "Failed to stop replica" caused by node is stopping

Alexander Belyak created IGNITE-20683: - Summary: "Failed to stop replica" caused by node is stopping Key: IGNITE-20683 URL: https://issues.apache.org/jira/browse/IGNITE-20683 Project: Ignite

[jira] [Assigned] (IGNITE-20639) Remove portRange from network configuration

[ https://issues.apache.org/jira/browse/IGNITE-20639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20639: -- Assignee: Mikhail Pochatkin > Remove portRange from network configuration >

[jira] [Updated] (IGNITE-20439) Sql. Support multiple schemas in CatalogSqlSchemaManager

[ https://issues.apache.org/jira/browse/IGNITE-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-20439: -- Summary: Sql. Support multiple schemas in CatalogSqlSchemaManager (was: Sql.

[jira] [Updated] (IGNITE-20671) Fix ItSqlApiBaseTest#ddl

[ https://issues.apache.org/jira/browse/IGNITE-20671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-20671: -- Fix Version/s: 3.0.0-beta2 > Fix ItSqlApiBaseTest#ddl > > >

[jira] [Updated] (IGNITE-20629) Exclude odbc build from common compilation

[ https://issues.apache.org/jira/browse/IGNITE-20629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20629: --- Description: {color:#172b4d}Current build via {color} {code:java} ./gradlew build

[jira] [Created] (IGNITE-20682) [ducktests] Add extension point to rebalance test

Sergey Korotkov created IGNITE-20682: Summary: [ducktests] Add extension point to rebalance test Key: IGNITE-20682 URL: https://issues.apache.org/jira/browse/IGNITE-20682 Project: Ignite

[jira] [Updated] (IGNITE-20470) Ducktape to check dump performance

[ https://issues.apache.org/jira/browse/IGNITE-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-20470: - Fix Version/s: 2.16 > Ducktape to check dump performance >

[jira] [Commented] (IGNITE-20470) Ducktape to check dump performance

[ https://issues.apache.org/jira/browse/IGNITE-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776622#comment-17776622 ] Nikolay Izhikov commented on IGNITE-20470: -- Merged to master. [~serge.korotkov] Thanks for

[jira] [Commented] (IGNITE-20002) Implement durable unlock on primary partition re-election

[ https://issues.apache.org/jira/browse/IGNITE-20002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776614#comment-17776614 ] Vladislav Pyatkov commented on IGNITE-20002: LGTM > Implement durable unlock on primary

[jira] [Created] (IGNITE-20681) Remove limit on cleanup attempts

Denis Chudov created IGNITE-20681: - Summary: Remove limit on cleanup attempts Key: IGNITE-20681 URL: https://issues.apache.org/jira/browse/IGNITE-20681 Project: Ignite Issue Type: Bug

[jira] [Commented] (IGNITE-20616) ensureReplicaIsPrimary should use getPrimaryReplica instead of awaitPrimaryReplica

[ https://issues.apache.org/jira/browse/IGNITE-20616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776590#comment-17776590 ] Alexander Lapin commented on IGNITE-20616: -- [~ktkale...@gridgain.com] LGTM >

[jira] [Assigned] (IGNITE-20609) Move last commit timestamp into BinaryRowMessage

[ https://issues.apache.org/jira/browse/IGNITE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20609: Assignee: Vladislav Pyatkov > Move last commit timestamp into

[jira] [Assigned] (IGNITE-20209) Catch-up rebalance triggers on node restart

[ https://issues.apache.org/jira/browse/IGNITE-20209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20209: Assignee: Kirill Gusakov > Catch-up rebalance triggers on node restart

[jira] [Assigned] (IGNITE-20210) Start partitions on corresponding assignments.stable, calculate if missing, cleanup obsolete resources

[ https://issues.apache.org/jira/browse/IGNITE-20210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20210: Assignee: Denis Chudov > Start partitions on corresponding

[jira] [Updated] (IGNITE-20605) Restore scaleUp/scaleDown timers

[ https://issues.apache.org/jira/browse/IGNITE-20605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-20605: - Description: h3. *Motivation* We need to restore timers that were scheduled

[jira] [Assigned] (IGNITE-20561) Change condition for DistributionZonesUtil#triggerKeyConditionForZonesChanges to use ConditionType#TOMBSTONE

[ https://issues.apache.org/jira/browse/IGNITE-20561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20561: Assignee: Mirza Aliev > Change condition for

[jira] [Assigned] (IGNITE-20599) Implement a 'NOT_TOMBSTONE' operation in the meta storage dsl.

[ https://issues.apache.org/jira/browse/IGNITE-20599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20599: Assignee: Mirza Aliev > Implement a 'NOT_TOMBSTONE' operation in the

[jira] [Updated] (IGNITE-20395) Clean up write intents for RW transaction on primary

[ https://issues.apache.org/jira/browse/IGNITE-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-20395: - Description: If a transaction was committed/aborted, but for any reason the

[jira] [Updated] (IGNITE-20680) Move table to RO state when executing DROP TABLE

[ https://issues.apache.org/jira/browse/IGNITE-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-20680: --- Epic Link: IGNITE-20473 > Move table to RO state when executing DROP TABLE >

[jira] [Commented] (IGNITE-20659) Placement driver do not create a lease

[ https://issues.apache.org/jira/browse/IGNITE-20659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776542#comment-17776542 ] Vladislav Pyatkov commented on IGNITE-20659: Merged

[jira] [Created] (IGNITE-20680) Move table to RO state when executing DROP TABLE

Roman Puchkovskiy created IGNITE-20680: -- Summary: Move table to RO state when executing DROP TABLE Key: IGNITE-20680 URL: https://issues.apache.org/jira/browse/IGNITE-20680 Project: Ignite

[jira] [Commented] (IGNITE-20530) Start building indexes for write-only indexes

[ https://issues.apache.org/jira/browse/IGNITE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776521#comment-17776521 ] Roman Puchkovskiy commented on IGNITE-20530: The patch looks good to me > Start building

[jira] [Assigned] (IGNITE-20439) Sql. Support multiple schemas in CatalogSqlSchemaManager.

[ https://issues.apache.org/jira/browse/IGNITE-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-20439: - Assignee: Konstantin Orlov > Sql. Support multiple schemas in

[jira] [Updated] (IGNITE-20439) Sql. Support multiple schemas in CatalogSqlSchemaManager.

[ https://issues.apache.org/jira/browse/IGNITE-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-20439: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Sql. Support multiple

[jira] [Commented] (IGNITE-20677) Sql. Improve error reporting in assertThrowsSqlException.

[ https://issues.apache.org/jira/browse/IGNITE-20677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776515#comment-17776515 ] Maksim Zhuravkov commented on IGNITE-20677: --- [~jooger] Could you please review my PR? > Sql.