[jira] [Resolved] (IGNITE-21010) Cluster loses connectivity after some time

[ https://issues.apache.org/jira/browse/IGNITE-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy resolved IGNITE-21010. Resolution: Fixed The issue is not reproducible anymore after IGNITE-21106 has

[jira] [Commented] (IGNITE-21010) Cluster loses connectivity after some time

[ https://issues.apache.org/jira/browse/IGNITE-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1785#comment-1785 ] Roman Puchkovskiy commented on IGNITE-21010: A bunch of issues were created after

[jira] [Updated] (IGNITE-21144) PartitionReplicaListener should return execution to partition thread pool after calls to PlacementDriver

[ https://issues.apache.org/jira/browse/IGNITE-21144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21144: --- Labels: ignite-3 storage-threading threading (was: ignite-3) >

[jira] [Updated] (IGNITE-20373) Fix IO threading model

[ https://issues.apache.org/jira/browse/IGNITE-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-20373: --- Labels: ignite-3 ignite3_performance threading (was: ignite-3

[jira] [Updated] (IGNITE-21079) PartitionReplicaListener should not interact with storages in the messaging thread

[ https://issues.apache.org/jira/browse/IGNITE-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21079: --- Labels: ignite-3 (was: ignite-3 threading) > PartitionReplicaListener should not

[jira] [Updated] (IGNITE-21079) PartitionReplicaListener should not interact with storages in the messaging thread

[ https://issues.apache.org/jira/browse/IGNITE-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21079: --- Labels: ignite-3 storage-threading threading (was: ignite-3) >

[jira] [Updated] (IGNITE-21079) PartitionReplicaListener should not interact with storages in the messaging thread

[ https://issues.apache.org/jira/browse/IGNITE-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21079: --- Labels: ignite-3 threading (was: ignite-3) > PartitionReplicaListener should not

[jira] [Updated] (IGNITE-21144) PartitionReplicaListener should return execution to partition thread pool after calls to PlacementDriver

[ https://issues.apache.org/jira/browse/IGNITE-21144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21144: --- Description: Futures returned by the PlacementDriver might be completed in the

[jira] [Created] (IGNITE-21144) PartitionReplicaListener should return execution to partition thread pool after calls to PlacementDriver

Roman Puchkovskiy created IGNITE-21144: -- Summary: PartitionReplicaListener should return execution to partition thread pool after calls to PlacementDriver Key: IGNITE-21144 URL:

[jira] [Updated] (IGNITE-21093) Remove MvccMessage

[ https://issues.apache.org/jira/browse/IGNITE-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21093: Description: Remove MvccMessage (was: Remove *.mvcc()) > Remove MvccMessage >

[jira] [Updated] (IGNITE-21093) Remove MvccMessage

[ https://issues.apache.org/jira/browse/IGNITE-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21093: Ignite Flags: (was: Docs Required,Release Notes Required) > Remove MvccMessage >

[jira] [Updated] (IGNITE-21093) Remove MvccMessage

[ https://issues.apache.org/jira/browse/IGNITE-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-21093: Summary: Remove MvccMessage (was: *.mvcc() removal) > Remove MvccMessage >

[jira] [Commented] (IGNITE-21093) *.mvcc() removal

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

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Description: It should be guaranteed that `CdcManager` handle all WAL records in the

[jira] [Comment Edited] (IGNITE-20477) Async component start

[ https://issues.apache.org/jira/browse/IGNITE-20477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793630#comment-17793630 ] Mirza Aliev edited comment on IGNITE-20477 at 12/22/23 2:57 PM: Please

[jira] [Updated] (IGNITE-20978) Send ScaleCube messages in a separate channel

[ https://issues.apache.org/jira/browse/IGNITE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-20978: --- Summary: Send ScaleCube messages in a separate channel (was: Process ScaleCube

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Description: It should be guaranteed that `CdcManager` handle all WAL records in the

[jira] [Updated] (IGNITE-21052) Sql. Test ExecutionServiceImplTest.testErrorIsPropagatedToPrefetchCallback is flaky due to planning timeout

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

[jira] [Created] (IGNITE-21143) SQL: Backslash cannot be escaped in LIKE ESCAPE operator

Andrey Khitrin created IGNITE-21143: --- Summary: SQL: Backslash cannot be escaped in LIKE ESCAPE operator Key: IGNITE-21143 URL: https://issues.apache.org/jira/browse/IGNITE-21143 Project: Ignite

[jira] [Created] (IGNITE-21142) "SqlException: Table with name 'N' already exists" upon creating a non-existing table

Ivan Artiukhov created IGNITE-21142: --- Summary: "SqlException: Table with name 'N' already exists" upon creating a non-existing table Key: IGNITE-21142 URL: https://issues.apache.org/jira/browse/IGNITE-21142

[jira] [Commented] (IGNITE-20883) ItDataSchemaSyncTest.checkSchemasCorrectlyRestore() is flaky with The query was cancelled while executing

[ https://issues.apache.org/jira/browse/IGNITE-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799838#comment-17799838 ]  Kirill Sizov commented on IGNITE-20883: {noformat} Caused by:

[jira] [Updated] (IGNITE-20894) Add tests for ensuring transactional guarantees

[ https://issues.apache.org/jira/browse/IGNITE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20894: --- Description: h3. Motivation The first purpose of the transaction flow tests is to

[jira] [Updated] (IGNITE-21141) MvccProcessor removal

[ https://issues.apache.org/jira/browse/IGNITE-21141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-21141: --- Description: Remove MvccProcessor class. (was: Remove TxLog region [1, TxLog] and all

[jira] [Commented] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

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

[jira] [Created] (IGNITE-21141) MvccProcessor removal

Ilya Shishkov created IGNITE-21141: -- Summary: MvccProcessor removal Key: IGNITE-21141 URL: https://issues.apache.org/jira/browse/IGNITE-21141 Project: Ignite Issue Type: Sub-task

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Description: It should be guaranteed that `CdcManager` handle all WAL records in the

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Description: It should be guaranteed that `CdcManager` handle all WAL records in the

[jira] [Commented] (IGNITE-20834) SQL query may hang forerver after node restart

[ https://issues.apache.org/jira/browse/IGNITE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799834#comment-17799834 ] Andrey Khitrin commented on IGNITE-20834: - Fixed > SQL query may hang forerver after node

[jira] [Resolved] (IGNITE-20834) SQL query may hang forerver after node restart

[ https://issues.apache.org/jira/browse/IGNITE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Khitrin resolved IGNITE-20834. - Resolution: Fixed > SQL query may hang forerver after node restart >

[jira] [Closed] (IGNITE-20834) SQL query may hang forerver after node restart

[ https://issues.apache.org/jira/browse/IGNITE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Khitrin closed IGNITE-20834. --- > SQL query may hang forerver after node restart >

[jira] [Updated] (IGNITE-20894) Add tests for ensuring transactional guarantees

[ https://issues.apache.org/jira/browse/IGNITE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20894: --- Description: Here is a list of tests that should be present: # Ensure the

[jira] [Updated] (IGNITE-20894) Add tests for ensuring transactional guarantees

[ https://issues.apache.org/jira/browse/IGNITE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20894: --- Summary: Add tests for ensuring transactional guarantees (was: Fix deadlock

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Description: It should be guaranteed that `CdcManager` handle all WAL records in the

[jira] [Commented] (IGNITE-20412) Fix DistributionZoneCausalityDataNodesTest.java#checkDataNodesRepeated

[ https://issues.apache.org/jira/browse/IGNITE-20412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799830#comment-17799830 ] Mirza Aliev commented on IGNITE-20412: -- LGTM > Fix

[jira] [Created] (IGNITE-21140) Ignite 3 Disaster Recovery

Ivan Bessonov created IGNITE-21140: -- Summary: Ignite 3 Disaster Recovery Key: IGNITE-21140 URL: https://issues.apache.org/jira/browse/IGNITE-21140 Project: Ignite Issue Type: Epic

[jira] [Updated] (IGNITE-21137) InternalTableImpl scan methods ignore 'columnsToInclude' parameter

[ https://issues.apache.org/jira/browse/IGNITE-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-21137: - Description: InternalTableImpl's scan methods are currently returning all columns,

[jira] [Updated] (IGNITE-21139) Provide ability to extract a command argument and class from management task event

[ https://issues.apache.org/jira/browse/IGNITE-21139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Amelchev updated IGNITE-21139: - Labels: ise (was: ) > Provide ability to extract a command argument and class from

[jira] [Created] (IGNITE-21139) Provide ability to extract a command argument and class from management task event

Nikita Amelchev created IGNITE-21139: Summary: Provide ability to extract a command argument and class from management task event Key: IGNITE-21139 URL: https://issues.apache.org/jira/browse/IGNITE-21139

[jira] [Updated] (IGNITE-21139) Provide ability to extract a command argument and class from management task event

[ https://issues.apache.org/jira/browse/IGNITE-21139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Amelchev updated IGNITE-21139: - Fix Version/s: 2.17 > Provide ability to extract a command argument and class from

[jira] [Updated] (IGNITE-21138) Complete handshake future with NodeStoppingException if rejecting a handshake due to stopping

[ https://issues.apache.org/jira/browse/IGNITE-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21138: --- Description: When we establish a connection from node A to B, the initial stages

[jira] [Updated] (IGNITE-21138) Complete handshake future with NodeStoppingException if rejecting a handshake due to stopping

[ https://issues.apache.org/jira/browse/IGNITE-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21138: --- Summary: Complete handshake future with NodeStoppingException if rejecting a

[jira] [Updated] (IGNITE-21033) .NET: Thin 3.0: TestClientRetriesComputeJobOnPrimaryAndDefaultNodes is broken due to notification mechanism

[ https://issues.apache.org/jira/browse/IGNITE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21033: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Thin 3.0:

[jira] [Commented] (IGNITE-21033) .NET: Thin 3.0: TestClientRetriesComputeJobOnPrimaryAndDefaultNodes is broken due to notification mechanism

[ https://issues.apache.org/jira/browse/IGNITE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799822#comment-17799822 ] Pavel Tupitsyn commented on IGNITE-21033: - Merged to main:

[jira] [Commented] (IGNITE-21034) Java thin 3.0: testClientRetriesComputeJobOnPrimaryAndDefaultNodes is broken due to notification mechanism

[ https://issues.apache.org/jira/browse/IGNITE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799817#comment-17799817 ] Pavel Tupitsyn commented on IGNITE-21034: - Merged to main:

[jira] [Commented] (IGNITE-21033) .NET: Thin 3.0: TestClientRetriesComputeJobOnPrimaryAndDefaultNodes is broken due to notification mechanism

[ https://issues.apache.org/jira/browse/IGNITE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799813#comment-17799813 ] Igor Sapego commented on IGNITE-21033: -- Looks good to me. > .NET: Thin 3.0:

[jira] [Updated] (IGNITE-21138) Complete client-side handshake future with NodeStoppingException if rejecting a handshake due to stopping

[ https://issues.apache.org/jira/browse/IGNITE-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21138: --- Description: When we establish a connection from node A to B, the initial stages

[jira] [Created] (IGNITE-21138) Complete client-side handshake future with NodeStoppingException if rejecting a handshake due to stopping

Roman Puchkovskiy created IGNITE-21138: -- Summary: Complete client-side handshake future with NodeStoppingException if rejecting a handshake due to stopping Key: IGNITE-21138 URL:

[jira] [Commented] (IGNITE-21034) Java thin 3.0: testClientRetriesComputeJobOnPrimaryAndDefaultNodes is broken due to notification mechanism

[ https://issues.apache.org/jira/browse/IGNITE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799804#comment-17799804 ] Igor Sapego commented on IGNITE-21034: -- Looks good to me. > Java thin 3.0:

[jira] [Updated] (IGNITE-21002) Document the ability to execute SQL multi-statement queries.

[ https://issues.apache.org/jira/browse/IGNITE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-21002: -- Description: We need to add documentation about the ability to execute SQL scripts.

[jira] [Updated] (IGNITE-21002) Document the ability to execute SQL multi-statement queries.

[ https://issues.apache.org/jira/browse/IGNITE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-21002: -- Description: We need to add documentation about the ability to execute SQL scripts.

[jira] [Updated] (IGNITE-21002) Document the ability to execute SQL multi-statement queries.

[ https://issues.apache.org/jira/browse/IGNITE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-21002: -- Description: We need to add documentation about the ability to execute SQL scripts.

[jira] [Updated] (IGNITE-21135) CdcManager might collect WAL data before restoring it's state

[ https://issues.apache.org/jira/browse/IGNITE-21135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-21135: Labels: ise (was: ) > CdcManager might collect WAL data before restoring it's state >

[jira] [Created] (IGNITE-21137) InternalTableImpl scan methods ignore 'columnsToInclude' parameter

Ivan Gagarkin created IGNITE-21137: -- Summary: InternalTableImpl scan methods ignore 'columnsToInclude' parameter Key: IGNITE-21137 URL: https://issues.apache.org/jira/browse/IGNITE-21137 Project:

[jira] [Created] (IGNITE-21136) SQL: implement functions for date/time formatting

Andrey Khitrin created IGNITE-21136: --- Summary: SQL: implement functions for date/time formatting Key: IGNITE-21136 URL: https://issues.apache.org/jira/browse/IGNITE-21136 Project: Ignite