[jira] [Commented] (IGNITE-20145) Update maven surefire version

[ https://issues.apache.org/jira/browse/IGNITE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753325#comment-17753325 ] Nikita Amelchev commented on IGNITE-20145: -- The {{-DforkMode=always}} property

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Node f

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Priority: Critical (was: Major) > Node failure when incorrect names are used for hitrate a

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Created] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

Ilya Shishkov created IGNITE-20201: -- Summary: Node failure when incorrect names are used for hitrate and histogram metrics configuration Key: IGNITE-20201 URL: https://issues.apache.org/jira/browse/IGNITE-20201

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Description: There are no metric name validation when we perform hitrate and historgam met

[jira] [Updated] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration

[ https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-20201: --- Issue Type: Bug (was: Improvement) > Node failure when incorrect names are used for hitrat

[jira] [Commented] (IGNITE-20200) Muted tests on TC lead to failed builds

[ https://issues.apache.org/jira/browse/IGNITE-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753255#comment-17753255 ] Pavel Tupitsyn commented on IGNITE-20200: - Merged to main: 027bdd16819ff8a6d811

[jira] [Updated] (IGNITE-20200) Muted tests on TC lead to failed builds

[ https://issues.apache.org/jira/browse/IGNITE-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20200: Fix Version/s: 3.0.0-beta2 > Muted tests on TC lead to failed builds > --

[jira] [Comment Edited] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev edited comment on IGNITE-20165 at 8/11/23 2:51 PM: --

[jira] [Created] (IGNITE-20200) Muted tests on TC lead to failed builds

Aleksandr Polovtcev created IGNITE-20200: Summary: Muted tests on TC lead to failed builds Key: IGNITE-20200 URL: https://issues.apache.org/jira/browse/IGNITE-20200 Project: Ignite Is

[jira] [Updated] (IGNITE-20200) Muted tests on TC lead to failed builds

[ https://issues.apache.org/jira/browse/IGNITE-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-20200: - Ignite Flags: (was: Docs Required,Release Notes Required) > Muted tests on TC

[jira] [Updated] (IGNITE-20200) Muted tests on TC lead to failed builds

[ https://issues.apache.org/jira/browse/IGNITE-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-20200: - Labels: ignite-3 (was: ) > Muted tests on TC lead to failed builds > -

[jira] [Comment Edited] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev edited comment on IGNITE-20165 at 8/11/23 2:35 PM: --

[jira] [Updated] (IGNITE-20199) Do not return updating rebalance assignments futures in DistributionZoneRebalanceEngine#onUpdateReplicas

[ https://issues.apache.org/jira/browse/IGNITE-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-20199: - Summary: Do not return updating rebalance assignments futures in DistributionZoneRebalanceEngin

[jira] [Updated] (IGNITE-20199) Do not return updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas

[ https://issues.apache.org/jira/browse/IGNITE-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-20199: - Summary: Do not return updating rebalance assignments future in DistributionZoneRebalanceEngine

[jira] [Updated] (IGNITE-20199) Do not chain updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas

[ https://issues.apache.org/jira/browse/IGNITE-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-20199: - Description: Seems that the current logic in {{DistributionZoneRebalanceEngine#onUpdateReplica

[jira] [Commented] (IGNITE-20053) Empty data nodes are returned by data nodes engine

[ https://issues.apache.org/jira/browse/IGNITE-20053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753243#comment-17753243 ] Kirill Gusakov commented on IGNITE-20053: - LGTM > Empty data nodes are returne

[jira] [Updated] (IGNITE-20199) Do not chain updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas

[ https://issues.apache.org/jira/browse/IGNITE-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-20199: - Description: After IGNITE-19506 was merged, it added the regression.  Previously we haven't re

[jira] [Created] (IGNITE-20199) Do not chain updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas

Mirza Aliev created IGNITE-20199: Summary: Do not chain updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas Key: IGNITE-20199 URL: https://issues.apache.org/jira/browse/IGNIT

[jira] [Updated] (IGNITE-20199) Do not chain updating rebalance assignments future in DistributionZoneRebalanceEngine#onUpdateReplicas

[ https://issues.apache.org/jira/browse/IGNITE-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-20199: - Description: After IGNITE-19506 was merged, it added the regression.  Previously we haven't re

[jira] [Comment Edited] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev edited comment on IGNITE-20165 at 8/11/23 2:00 PM: --

[jira] [Comment Edited] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev edited comment on IGNITE-20165 at 8/11/23 1:59 PM: --

[jira] [Comment Edited] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev edited comment on IGNITE-20165 at 8/11/23 1:58 PM: --

[jira] [Updated] (IGNITE-19919) org.apache.ignite.sql.ResultSet#close should close implicit transaction if any

[ https://issues.apache.org/jira/browse/IGNITE-19919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-19919: -- Fix Version/s: 3.0.0-beta2 > org.apache.ignite.sql.ResultSet#close should close impli

[jira] [Commented] (IGNITE-20035) IndexOutOfBoundsException when statement.SetMaxRows is set

[ https://issues.apache.org/jira/browse/IGNITE-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753236#comment-17753236 ] Pavel Pereslegin commented on IGNITE-20035: --- [~mzhuravkov], [~amashenkov], pl

[jira] [Commented] (IGNITE-20165) Revisit the configuration of thread pools used by JRaft

[ https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753233#comment-17753233 ] Mirza Aliev commented on IGNITE-20165: -- ||Pool name||Description||Number of Thread

[jira] [Comment Edited] (IGNITE-19919) org.apache.ignite.sql.ResultSet#close should close implicit transaction if any

[ https://issues.apache.org/jira/browse/IGNITE-19919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753230#comment-17753230 ] Pavel Pereslegin edited comment on IGNITE-19919 at 8/11/23 1:45 PM: -

[jira] [Commented] (IGNITE-20194) Calcite engine. Dependency common-codec required for some functions

[ https://issues.apache.org/jira/browse/IGNITE-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753227#comment-17753227 ] Ignite TC Bot commented on IGNITE-20194: {panel:title=Branch: [pull/10889/head]

[jira] [Assigned] (IGNITE-20015) Sql. Introduce new distribution function

[ https://issues.apache.org/jira/browse/IGNITE-20015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-20015: - Assignee: Andrey Mashenkov > Sql. Introduce new distribution function > --

[jira] [Updated] (IGNITE-19789) Sql. Introduce RowSchema for RowFactory

[ https://issues.apache.org/jira/browse/IGNITE-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19789: -- Fix Version/s: 3.0.0-beta2 > Sql. Introduce RowSchema for RowFactory > --

[jira] [Assigned] (IGNITE-20198) .NET: Frequent failures in Plaform .NET (Core Linux) TC Project

[ https://issues.apache.org/jira/browse/IGNITE-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-20198: --- Assignee: Pavel Tupitsyn > .NET: Frequent failures in Plaform .NET (Core Linux) TC

[jira] [Updated] (IGNITE-20198) .NET: Frequent failures in Plaform .NET (Core Linux) TC Project

[ https://issues.apache.org/jira/browse/IGNITE-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20198: Component/s: platforms (was: .NET) > .NET: Frequent failures in Plaf

[jira] [Updated] (IGNITE-20198) .NET: Frequent failures in Plaform .NET (Core Linux) TC Project

[ https://issues.apache.org/jira/browse/IGNITE-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20198: Labels: .NET (was: ) > .NET: Frequent failures in Plaform .NET (Core Linux) TC Project >

[jira] [Updated] (IGNITE-20198) .NET: Frequent failures in Plaform .NET (Core Linux) TC Project

[ https://issues.apache.org/jira/browse/IGNITE-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20198: Fix Version/s: 2.16 > .NET: Frequent failures in Plaform .NET (Core Linux) TC Project > -

[jira] [Updated] (IGNITE-20198) .NET: Frequent failures in Plaform .NET (Core Linux) TC Project

[ https://issues.apache.org/jira/browse/IGNITE-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20198: Summary: .NET: Frequent failures in Plaform .NET (Core Linux) TC Project (was: .NET Freq

[jira] [Updated] (IGNITE-20197) .NET: Thin 3.0: Perf: Excessive dictionary lookups by GetFieldByColumnName usages

[ https://issues.apache.org/jira/browse/IGNITE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20197: Summary: .NET: Thin 3.0: Perf: Excessive dictionary lookups by GetFieldByColumnName usage

[jira] [Updated] (IGNITE-20197) .NET: Thin 3.0: Excessive dictionary lookups by GetFieldByColumnName usages

[ https://issues.apache.org/jira/browse/IGNITE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20197: Description: All usages of [ReflectionUtils.GetFieldByColumnName|https://github.com/apac

[jira] [Created] (IGNITE-20198) .NET Frequent failures in Plaform .NET (Core Linux) TC Project

Andrey Khitrin created IGNITE-20198: --- Summary: .NET Frequent failures in Plaform .NET (Core Linux) TC Project Key: IGNITE-20198 URL: https://issues.apache.org/jira/browse/IGNITE-20198 Project: Ignit

[jira] [Updated] (IGNITE-20197) .NET: Thin 3.0: Excessive dictionary lookups by GetFieldByColumnName usages

[ https://issues.apache.org/jira/browse/IGNITE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20197: Description: All callers of > .NET: Thin 3.0: Excessive dictionary lookups by GetFieldBy

[jira] [Created] (IGNITE-20197) .NET: Thin 3.0: Excessive dictionary lookups by GetFieldByColumnName usages

Pavel Tupitsyn created IGNITE-20197: --- Summary: .NET: Thin 3.0: Excessive dictionary lookups by GetFieldByColumnName usages Key: IGNITE-20197 URL: https://issues.apache.org/jira/browse/IGNITE-20197 P

[jira] [Created] (IGNITE-20196) Sql. Review list of reserver keywords

Konstantin Orlov created IGNITE-20196: - Summary: Sql. Review list of reserver keywords Key: IGNITE-20196 URL: https://issues.apache.org/jira/browse/IGNITE-20196 Project: Ignite Issue Type

[jira] [Resolved] (IGNITE-18989) Design table management flow (part 2)

[ https://issues.apache.org/jira/browse/IGNITE-18989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-18989. -- Resolution: Won't Do > Design table management flow (part 2) > --

[jira] [Commented] (IGNITE-20189) Prepare existing tests for the distributed zone to switch to the catalog #2

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

[jira] [Resolved] (IGNITE-20168) MultiActorPlacementDriverTest#testLeaseProlong is flaky

[ https://issues.apache.org/jira/browse/IGNITE-20168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-20168. -- Resolution: Cannot Reproduce > MultiActorPlacementDriverTest#testLeaseProlong

[jira] [Assigned] (IGNITE-19227) Wait for schema awailability out of JRaft threads

[ https://issues.apache.org/jira/browse/IGNITE-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-19227: -- Assignee: Roman Puchkovskiy > Wait for schema awailability out of JRaft thre

[jira] [Commented] (IGNITE-20178) Introduce param-free IgniteInternalFuture.listen(() -> {}) in addition to .listen((fut) -> {}) to avoid ignored params

[ https://issues.apache.org/jira/browse/IGNITE-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753107#comment-17753107 ] Ignite TC Bot commented on IGNITE-20178: {panel:title=Branch: [pull/10885/head]

[jira] [Created] (IGNITE-20195) Long fsync of Raft log storage

Denis Chudov created IGNITE-20195: - Summary: Long fsync of Raft log storage Key: IGNITE-20195 URL: https://issues.apache.org/jira/browse/IGNITE-20195 Project: Ignite Issue Type: Bug