[jira] [Created] (IGNITE-15770) SQL-escaped similar columns are ignored by BinaryMapper

Maksim Timonin created IGNITE-15770: --- Summary: SQL-escaped similar columns are ignored by BinaryMapper Key: IGNITE-15770 URL: https://issues.apache.org/jira/browse/IGNITE-15770 Project: Ignite

[jira] [Commented] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

[ https://issues.apache.org/jira/browse/IGNITE-14776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430181#comment-17430181 ] Pavel Tupitsyn commented on IGNITE-14776: - Cherry-picked to ignite-2.12:

[jira] [Commented] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

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

[jira] [Resolved] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

[ https://issues.apache.org/jira/browse/IGNITE-14776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-14776. - Resolution: Fixed > .NET: ClientFailoverSocket sets logger too late, resulting in null

[jira] [Commented] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

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

[jira] [Issue Comment Deleted] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

[ https://issues.apache.org/jira/browse/IGNITE-14776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14776: Comment: was deleted (was: {panel:title=Branch: [pull/9499/head] Base: [master] :

[jira] [Updated] (IGNITE-14872) Recalculation affinity based on topology events

[ https://issues.apache.org/jira/browse/IGNITE-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-14872: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-14873) Failover scenarios

[ https://issues.apache.org/jira/browse/IGNITE-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-14873: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15125) Implement naive partitions reassignment

[ https://issues.apache.org/jira/browse/IGNITE-15125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15125: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15514) Add guaranties of using appropriate affinity assignments from lagged node after reassignment.

[ https://issues.apache.org/jira/browse/IGNITE-15514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15514: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) > Add

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15495) Rebalance via raft log

[ https://issues.apache.org/jira/browse/IGNITE-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15495: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15494) Need to provide internal mechanism that allows to wait for rebalance

[ https://issues.apache.org/jira/browse/IGNITE-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15494: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15493) Need to clarify changePeers behavior to support the case with only one replica which should be moved during rebalance

[ https://issues.apache.org/jira/browse/IGNITE-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15493: - Issue Type: Task (was: Improvement) > Need to clarify changePeers behavior to support

[jira] [Updated] (IGNITE-15493) Need to clarify changePeers behavior to support the case with only one replica which should be moved during rebalance

[ https://issues.apache.org/jira/browse/IGNITE-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15493: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15492) Check schema availability on local node

[ https://issues.apache.org/jira/browse/IGNITE-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15492: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15491) Introduce IgniteCluster interface to manipulate baseline nodes

[ https://issues.apache.org/jira/browse/IGNITE-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15491: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was: Sub-task) >

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-14209) Data rebalancing

[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-14209: - Issue Type: Epic (was: New Feature) > Data rebalancing > > >

[jira] [Updated] (IGNITE-14209) Data rebalancing

[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-14209: - Epic Name: Data rebalancing > Data rebalancing > > >

[jira] [Updated] (IGNITE-15705) Investigate raft client timeouts

[ https://issues.apache.org/jira/browse/IGNITE-15705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15705: - Description: h3. Problem Raft client timeout should be large enough for the operation

[jira] [Updated] (IGNITE-15705) Investigate raft client timeouts

[ https://issues.apache.org/jira/browse/IGNITE-15705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15705: - Description: h3. Problem Raft client timeout should be large enough for the operation

[jira] [Updated] (IGNITE-15493) Need to clarify changePeers behavior to support the case with only one replica which should be moved during rebalance

[ https://issues.apache.org/jira/browse/IGNITE-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15493: - Description: Need to clarify the behavior of changePeers (IGNITE-15288) method in case

[jira] [Updated] (IGNITE-15493) Need to clarify changePeers behavior to support the case with only one replica which should be moved during rebalance

[ https://issues.apache.org/jira/browse/IGNITE-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15493: - Description: Need to clarify the behavior of changePeers (IGNITE-15288) method in case

[jira] [Commented] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

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

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Commented] (IGNITE-15443) Add Map with primitive keys implementations.

[ https://issues.apache.org/jira/browse/IGNITE-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430042#comment-17430042 ] Andrey Mashenkov commented on IGNITE-15443: --- [~aholod], the ticket is not in "in progress"

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15096) Schema events processing refactoring.

[ https://issues.apache.org/jira/browse/IGNITE-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15096: -- Description: All table events with schema events are processed in TableManager

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Assigned] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-15769: Assignee: Nikolay Izhikov > IgniteToIgniteCdcStreamer fails on complex keys >

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Priority: Blocker (was: Major) > IgniteToIgniteCdcStreamer fails on complex keys >

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Description: In case if complex key is used (i.e. custom class or composite primary key in

[jira] [Commented] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430036#comment-17430036 ] Andrey Mashenkov commented on IGNITE-15414: --- [~jooger], done. > Schema validation

[jira] [Updated] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15414: -- Description: 1. TableValidator code exists, but validator is never registered. Let's

[jira] [Updated] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15414: -- Description: 1. TableValidator code exists, but validator is never registered. Let's

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Description: In case if complex key is used (i.e. custom class or composite primary key in

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Attachment: CdcFailureOnComplexKey.html > IgniteToIgniteCdcStreamer fails on complex keys

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Description: In case if complex key is used (i.e. custom class or composite primary key in

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Description: In case if complex key is used (i.e. custom class or composite primary key in

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Description: In case if complex key is used (i.e. custom class or composite primary key in

[jira] [Updated] (IGNITE-15769) IgniteToIgniteCdcStreamer fails on complex keys

[ https://issues.apache.org/jira/browse/IGNITE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-15769: --- Summary: IgniteToIgniteCdcStreamer fails on complex keys (was: IgniteToIgniteCdcConsumer

[jira] [Updated] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15414: -- Description: 1. TableValidator code exists, but validator is never registered. Let's

[jira] [Created] (IGNITE-15769) IgniteToIgniteCdcConsumer fails on complex keys

Ilya Shishkov created IGNITE-15769: -- Summary: IgniteToIgniteCdcConsumer fails on complex keys Key: IGNITE-15769 URL: https://issues.apache.org/jira/browse/IGNITE-15769 Project: Ignite Issue

[jira] [Updated] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15414: -- Description: 1. TableValidator code exists, but validator is never registered. Let's

[jira] [Updated] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15414: -- Description: 1. TableValidator code exists, but validator is never registered. Let's

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15718) Issues in implementation of the method TableManager#table(String)

[ https://issues.apache.org/jira/browse/IGNITE-15718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15718: - Description: The method (TableManager#table(String)), where we are waiting for

[jira] [Commented] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430025#comment-17430025 ] Andrey Mashenkov commented on IGNITE-13667: --- [~korlov], Could you please review, does it look

[jira] [Updated] (IGNITE-15711) Implement Loza stop

[ https://issues.apache.org/jira/browse/IGNITE-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15711: - Description: My suggestions: # Add a busy lock on all public methods of Loza

[jira] [Updated] (IGNITE-15711) Implement Loza stop

[ https://issues.apache.org/jira/browse/IGNITE-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15711: - Description: My suggestions: # Add a busy lock on all public methods of Loza

[jira] [Updated] (IGNITE-15724) MetastorageManager uses incorrect predicate in order to create corresponding raft group service

[ https://issues.apache.org/jira/browse/IGNITE-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15724: - Description: Currently, when the {{MetaStorageManager}} is started, the

[jira] [Commented] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430016#comment-17430016 ] Yury Gerzhedovich commented on IGNITE-15414: [~amashenkov], let's actualize the description

[jira] [Commented] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430013#comment-17430013 ] Yury Gerzhedovich commented on IGNITE-13667: [~amashenkov], LGTM, except few comments in

[jira] [Commented] (IGNITE-15599) Get rid Guava in Calcite module

[ https://issues.apache.org/jira/browse/IGNITE-15599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430004#comment-17430004 ] Yury Gerzhedovich commented on IGNITE-15599: [~tledkov-gridgain], Looks good to me except

[jira] [Updated] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13667: -- Description: When a schema is defined, the key chunk columns and value chunk columns

[jira] [Updated] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13667: -- Description: When a schema is defined, the key chunk columns and value chunk columns

[jira] [Updated] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13667: -- Fix Version/s: 3.0 > Add schema columns mapping from user order to system order >

[jira] [Updated] (IGNITE-15768) Change get version script in nightly release build after IGNITE-15645

[ https://issues.apache.org/jira/browse/IGNITE-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15768: - Description: After IGNITE-15645,

[jira] [Comment Edited] (IGNITE-15746) Configuration: in-closure data validation

[ https://issues.apache.org/jira/browse/IGNITE-15746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429975#comment-17429975 ] Alexander Lapin edited comment on IGNITE-15746 at 10/18/21, 12:01 PM:

[jira] [Resolved] (IGNITE-15746) Configuration: in-closure data validation

[ https://issues.apache.org/jira/browse/IGNITE-15746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin resolved IGNITE-15746. -- Resolution: Duplicate Duplicates https://issues.apache.org/jira/browse/IGNITE-15746

[jira] [Updated] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream

[ https://issues.apache.org/jira/browse/IGNITE-14776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14776: Summary: .NET: ClientFailoverSocket sets logger too late, resulting in null loggers

[jira] [Updated] (IGNITE-14776) .NET: ClientFailoverSocket sets logger too late, resulting in null loggers downstream.

[ https://issues.apache.org/jira/browse/IGNITE-14776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14776: Priority: Critical (was: Major) > .NET: ClientFailoverSocket sets logger too late,

[jira] [Updated] (IGNITE-15490) Create an example(s) that can allow to demonstrate rebalancing from the end-user point of view

[ https://issues.apache.org/jira/browse/IGNITE-15490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15490: - Parent: (was: IGNITE-14209) Issue Type: Improvement (was:

[jira] [Assigned] (IGNITE-15600) Cache for Calcite SQL plans in 3.0

[ https://issues.apache.org/jira/browse/IGNITE-15600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-15600: - Assignee: Konstantin Orlov > Cache for Calcite SQL plans in 3.0 >

[jira] [Updated] (IGNITE-15768) Change get version script in nightly release build after IGNITE-15645

[ https://issues.apache.org/jira/browse/IGNITE-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15768: - Description: After IGNITE-15645,

[jira] [Assigned] (IGNITE-15768) Change get version script in nightly release build after IGNITE-15645

[ https://issues.apache.org/jira/browse/IGNITE-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky reassigned IGNITE-15768: Assignee: Petr Ivanov > Change get version script in nightly release build

[jira] [Created] (IGNITE-15768) Change get version script in nightly release build after IGNITE-15645

Ivan Daschinsky created IGNITE-15768: Summary: Change get version script in nightly release build after IGNITE-15645 Key: IGNITE-15768 URL: https://issues.apache.org/jira/browse/IGNITE-15768

[jira] [Commented] (IGNITE-15414) Schema validation refactoring with configuration validators

[ https://issues.apache.org/jira/browse/IGNITE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429944#comment-17429944 ] Andrey Mashenkov commented on IGNITE-15414: --- Most of described were refactored in

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-15572) Ability to set custom execution context for Ignite service.

[ https://issues.apache.org/jira/browse/IGNITE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-15572: -- Description: In traditional microservices, we have the ability to set a custom

[jira] [Updated] (IGNITE-13667) Add schema columns mapping from user order to system order

[ https://issues.apache.org/jira/browse/IGNITE-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13667: -- Summary: Add schema columns mapping from user order to system order (was: Add

[jira] [Assigned] (IGNITE-15767) Need to workaround JDK bug JDK-8247750

[ https://issues.apache.org/jira/browse/IGNITE-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-15767: -- Assignee: Ivan Bessonov > Need to workaround JDK bug JDK-8247750 >

[jira] [Updated] (IGNITE-15767) Need to workaround JDK bug JDK-8247750

[ https://issues.apache.org/jira/browse/IGNITE-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-15767: --- Description: See [https://bugs.openjdk.java.net/browse/JDK-8247750] ServerSocket.accept()

[jira] [Updated] (IGNITE-15767) Need to workaround JDK bug JDK-8247750

[ https://issues.apache.org/jira/browse/IGNITE-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-15767: --- Description: See [https://bugs.openjdk.java.net/browse/JDK-8247750] ServerSocket.accept()

[jira] [Created] (IGNITE-15767) Need to workaround JDK bug JDK-8247750

Ivan Bessonov created IGNITE-15767: -- Summary: Need to workaround JDK bug JDK-8247750 Key: IGNITE-15767 URL: https://issues.apache.org/jira/browse/IGNITE-15767 Project: Ignite Issue Type: