notifications  

Messages by Thread

• [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
  • Re: [PR] IGNITE-28194 Remove `ConfigurationModules` [ignite-3] via GitHub
• Re: [PR] IGNITE-27521 Java client: handle multiple endpoints for the same node [ignite-3] via GitHub
• Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
  • Re: [PR] IGNITE-27994 Create CLI command for REST endpoint to edit cluster name [ignite-3] via GitHub
• Re: [PR] IGNITE-28007 split TablePartitionResourcesFactory out of TableManager [ignite-3] via GitHub
  • Re: [PR] IGNITE-28007 split TablePartitionResourcesFactory out of TableManager [ignite-3] via GitHub
  • Re: [PR] IGNITE-28007 split TablePartitionResourcesFactory out of TableManager [ignite-3] via GitHub
  • Re: [PR] IGNITE-28007 split TablePartitionResourcesFactory out of TableManager [ignite-3] via GitHub
  • Re: [PR] IGNITE-28007 split TablePartitionResourcesFactory out of TableManager [ignite-3] via GitHub
• Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
  • Re: [PR] IGNITE-28117: Examples not self-contained - missing or broken setup/teardown causes state leakage [ignite-3] via GitHub
• [PR] IGNITE-28191 Fix flaky recreateTableWithTheSameName test [ignite-3] via GitHub
  • Re: [PR] IGNITE-28191 Fix flaky recreateTableWithTheSameName test [ignite-3] via GitHub
• [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Fine tuning for CI messages [ignite] via GitHub
• Re: [PR] Bump org.springframework.data:spring-data-jdbc from 3.5.5 to 4.0.3 [ignite-3] via GitHub
  • Re: [PR] Bump org.springframework.data:spring-data-jdbc from 3.5.5 to 4.0.3 [ignite-3] via GitHub
• Re: [PR] Bump spring-boot from 3.5.7 to 4.0.3 [ignite-3] via GitHub
  • Re: [PR] Bump spring-boot from 3.5.7 to 4.0.3 [ignite-3] via GitHub
• Re: [PR] Bump org.springframework.boot:spring-boot-dependencies from 4.0.2 to 4.0.3 [ignite-3] via GitHub
  • Re: [PR] Bump org.springframework.boot:spring-boot-dependencies from 4.0.2 to 4.0.3 [ignite-3] via GitHub
• Re: [PR] Bump mockito from 5.21.0 to 5.22.0 [ignite-3] via GitHub
• Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
  • Re: [PR] Ignite 28061 CI debug [ignite] via GitHub
• Re: [I] Vulnerability Report: Apache Ignite JDBC `cfg://` Remote Spring Configuration Leads to Arbitrary Code Execution [ignite] via GitHub
• [PR] Disable immediate send future completion [ignite-3] via GitHub
  • Re: [PR] Disable immediate send future completion [ignite-3] via GitHub
• Re: [PR] IGNITE-28040 Improve test coverage for alter table add columns [ignite-3] via GitHub
• Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
  • Re: [PR] IGNITE-27716: Add group name to DumpReader logs [ignite] via GitHub
• Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
  • Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
  • Re: [PR] IGNITE-28118 Add checkstyle rule to disallow TODO comments without ticket [ignite-3] via GitHub
• Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
  • Re: [PR] IGNITE-27386 Add failure reason to tx state meta [ignite-3] via GitHub
• Re: [PR] IGNITE-28097 Fixed unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixed unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
• [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 WIP [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
  • Re: [PR] IGNITE-28189 Fixed incorrect status of a Compute Task when it is canceled [ignite] via GitHub
• [PR] IGNITE-28188 Constant descriptors for messages code generation [ignite] via GitHub
  • Re: [PR] IGNITE-28188 Constant descriptors for messages code generation [ignite] via GitHub
• [PR] Added hashing to C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing to C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-28081 Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-28081 Added hashing functions for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-28081 Added hashing functions for C++ client [ignite-3] via GitHub
• [PR] IGNITE-28187 Non-transactional replica requests should be retried in the same manner as transactional [ignite-3] via GitHub
  • Re: [PR] IGNITE-28187 Non-transactional replica requests should be retried in the same manner as transactional [ignite-3] via GitHub
• Re: [PR] IGNITE-28116 update commons-lang3 [ignite] via GitHub
  • Re: [PR] IGNITE-28116 update commons-lang3 [ignite] via GitHub
• Re: [PR] IGNITE-28179 Add paged result fetching for CLI SQL [ignite-3] via GitHub
• Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27631 Use MessageSerializer for SingleNodeMessage [ignite] via GitHub
• Re: [PR] IGNITE-27966 Use message serializer for ClientCacheChangeDiscoveryMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27966 Use message serializer for ClientCacheChangeDiscoveryMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27966 Use message serializer for ClientCacheChangeDiscoveryMessage [ignite] via GitHub
• Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
  • Re: [PR] IGNITE-28114 Remove custom configuration for Apache RAT plugin [ignite] via GitHub
• Re: [PR] IGNITE-28061 Migrate ZookeeperDiscoverySpi to new serialization framework for discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28061 Migrate ZookeeperDiscoverySpi to new serialization framework for discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28061 Migrate ZookeeperDiscoverySpi to new serialization framework for discovery custom messages [ignite] via GitHub
• Re: [PR] IGNITE-27953 Use message serializer for CacheAffinityChangeMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27953 Use message serializer for CacheAffinityChangeMessage [ignite] via GitHub
• Re: [PR] IGNITE-27972 Use message serializer for MappingProposedMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27972 Use message serializer for MappingProposedMessage [ignite] via GitHub
• Re: [PR] IGNITE-28018 Github action hook to control changes inside the messages. [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Github action hook to control changes inside the messages. [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Github action hook to control changes inside the messages. [ignite] via GitHub
  • Re: [PR] IGNITE-28018 Github action hook to control changes inside the messages. [ignite] via GitHub
• [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
  • Re: [PR] IGNITE-27964 Use index-based approach in RaftLogGarbageCollector [ignite-3] via GitHub
• Re: [PR] IGNITE-27971 Use message serializer for MappingAcceptedMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27971 Use message serializer for MappingAcceptedMessage [ignite] via GitHub
• Re: [PR] IGNITE-27900 Use message serializer for CacheStatisticsClearMessage [ignite] via GitHub
• [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
  • Re: [PR] IGNITE-28186 DeploymentSPI marked as deprecated [ignite] via GitHub
• Re: [PR] IGNITE-28080 Upgrade to Maven 3.9.6 [ignite] via GitHub
  • Re: [PR] IGNITE-28080 Upgrade to Maven 3.9.6 [ignite] via GitHub
• Re: [PR] IGNITE-26060 FailureHandler isn't called on TX coordinator node in certain scenarios [ignite] via GitHub
  • Re: [PR] IGNITE-26060 FailureHandler isn't called on TX coordinator node in certain scenarios [ignite] via GitHub
  • Re: [PR] IGNITE-26060 FailureHandler isn't called on TX coordinator node in certain scenarios [ignite] via GitHub
• Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage v3 - codegen [ignite] via GitHub
  • Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage v3 - codegen [ignite] via GitHub
• Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage v2 [ignite] via GitHub
  • Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage v2 [ignite] via GitHub
• Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage [ignite] via GitHub
  • Re: [PR] IGNITE-27414 : Use MessageSerializer for TcpDiscoveryClientReconnectMessage [ignite] via GitHub
• Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
  • Re: [PR] IGNITE-28097 Fixeв unclosed socket if the client node stopped during a reconnect. [ignite] via GitHub
• Re: [PR] IGNITE-27951: Upgrade Jetty to 11.0.25 and tomcat-servlet-api to 10.0.27 [ignite] via GitHub
  • Re: [PR] IGNITE-27951: Upgrade Jetty to 11.0.25 and tomcat-servlet-api to 10.0.27 [ignite] via GitHub
  • Re: [PR] IGNITE-27951: Upgrade Jetty to 11.0.25 and tomcat-servlet-api to 10.0.27 [ignite] via GitHub
  • Re: [PR] IGNITE-27951: Upgrade Jetty to 11.0.25 and tomcat-servlet-api to 10.0.27 [ignite] via GitHub
  • Re: [PR] IGNITE-27951: Upgrade Jetty to 11.0.25 and tomcat-servlet-api to 10.0.27 [ignite] via GitHub

• Later messages