notifications  

Messages by Thread

• • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
  • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
  • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
  • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
  • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
  • Re: [PR] IGNITE-25978 Optimize implicit RO transaction flow [ignite-3] via GitHub
• [PR] IGNITE-25890 .NET: Add ISql.ExecuteBatchAsync [ignite-3] via GitHub
  • Re: [PR] IGNITE-25890 .NET: Add ISql.ExecuteBatchAsync [ignite-3] via GitHub
  • Re: [PR] IGNITE-25890 .NET: Add ISql.ExecuteBatchAsync [ignite-3] via GitHub
• [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
  • Re: [PR] IGNITE-26006 Configuration compatibility. Correctly handle adding new fields in compatibility test [ignite-3] via GitHub
• [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
  • Re: [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
  • Re: [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
  • Re: [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
  • Re: [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
  • Re: [PR] IGNITE-26003 Fix JavaThinCompatibilityTest#testOldClientToCurrentServ… [ignite] via GitHub
• [PR] IGNITE-25896 Sql. Make root node support project with duplicate names. [ignite-3] via GitHub
  • Re: [PR] IGNITE-25896 Sql. Make root node support project with duplicate names. [ignite-3] via GitHub
• [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
  • Re: [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
  • Re: [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
  • Re: [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
  • Re: [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
  • Re: [PR] IGNITE-25992 Use MessageSerializer for GridCacheVersion and GridCacheVersionEx [ignite] via GitHub
• [PR] IGNITE-26001 Simplify event log API [ignite-3] via GitHub
  • Re: [PR] IGNITE-26001 Simplify event log API [ignite-3] via GitHub
• [PR] IGNITE-25958 Fix exclusions in IgniteCompatibilityAbstractTest [ignite] via GitHub
  • Re: [PR] IGNITE-25958 Fix exclusions in IgniteCompatibilityAbstractTest [ignite] via GitHub
  • Re: [PR] IGNITE-25958 Fix exclusions in IgniteCompatibilityAbstractTest [ignite] via GitHub
  • Re: [PR] IGNITE-25958 Fix exclusions in IgniteCompatibilityAbstractTest [ignite] via GitHub
  • Re: [PR] IGNITE-25958 Fix exclusions in IgniteCompatibilityAbstractTest [ignite] via GitHub
• [PR] [MINOR] Minify visibility of BinaryUtils doReadXXXArray methods [ignite] via GitHub
  • Re: [PR] [MINOR] Minify visibility of BinaryUtils doReadXXXArray methods [ignite] via GitHub
  • Re: [PR] [MINOR] Minify visibility of BinaryUtils doReadXXXArray methods [ignite] via GitHub
• [PR] IGNITE-25997 Improve compatibility test resolution [ignite-3] via GitHub
  • Re: [PR] IGNITE-25997 Improve compatibility test resolution [ignite-3] via GitHub
• [PR] IGNITE-25998 Add igniteClient examples [ignite-3] via GitHub
  • Re: [PR] IGNITE-25998 Add igniteClient examples [ignite-3] via GitHub
  • Re: [PR] IGNITE-25998 Add java client examples [ignite-3] via GitHub
• [PR] IGNITE-25939 Add the metric sources for background activity: leases and transaction resource vacuumizer [ignite-3] via GitHub
  • Re: [PR] IGNITE-25939 Add the metric sources for background activity: leases and transaction resource vacuumizer [ignite-3] via GitHub
  • Re: [PR] IGNITE-25939 Add the metric sources for background activity: leases and transaction resource vacuumizer [ignite-3] via GitHub
  • Re: [PR] IGNITE-25939 Add the metric sources for background activity: leases and transaction resource vacuumizer [ignite-3] via GitHub
  • Re: [PR] IGNITE-25939 Add the metric sources for background activity: leases and transaction resource vacuumizer [ignite-3] via GitHub
• [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
  • Re: [PR] IGNITE-25972 Support error code aliases and deprecation [ignite-3] via GitHub
• [PR] IGNITE-25470 AI3. Remove useless system properties related to logging [ignite-3] via GitHub
  • Re: [PR] IGNITE-25470 AI3. Remove useless system properties related to logging [ignite-3] via GitHub
• [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
  • Re: [PR] IGNITE-25895 Implement method to get on-disk tables/zones IDs in Raft log storage [ignite-3] via GitHub
• [I] C++ thin Client (2.17.0) - Slow write throughput [ignite] via GitHub
• [PR] IGNITE-25932 .NET: Fix TestJobExecutionStatusExecuting flakiness on Windows [ignite-3] via GitHub
  • Re: [PR] IGNITE-25932 .NET: Fix TestJobExecutionStatusExecuting flakiness on Windows [ignite-3] via GitHub
• [I] no need [ignite] via GitHub
  • Re: [I] no need [ignite] via GitHub
• Re: [I] Apache Ignite 3.0 - Reading Data from ignite via C++ Client [ignite] via GitHub
• [PR] IGNITE-25941 .NET: Fix pooled buffer bugs [ignite-3] via GitHub
  • Re: [PR] IGNITE-25941 .NET: Fix pooled buffer bugs [ignite-3] via GitHub
  • Re: [PR] IGNITE-25941 .NET: Fix pooled buffer bugs [ignite-3] via GitHub
• [PR] IGNITE-25586 Sql. Partition awareness. Performance tests [ignite-3] via GitHub
  • Re: [PR] IGNITE-25586 Sql. Partition awareness. Performance tests [ignite-3] via GitHub
  • Re: [PR] IGNITE-25586 Sql. Partition awareness. Performance tests [ignite-3] via GitHub
  • Re: [PR] IGNITE-25586 Sql. Partition awareness. Performance tests [ignite-3] via GitHub
• [PR] IGNITE-25389 Compilation fix [ignite-extensions] via GitHub
  • Re: [PR] IGNITE-25389 Compilation fix [ignite-extensions] via GitHub
• [PR] Bump org.junit.platform:junit-platform-testkit from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-testkit from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-testkit from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-testkit from 1.13.3 to 1.13.4 [ignite-3] via GitHub
• [PR] Bump org.junit.platform:junit-platform-console from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-console from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-console from 1.13.3 to 1.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump org.junit.platform:junit-platform-console from 1.13.3 to 1.13.4 [ignite-3] via GitHub
• [PR] Bump jackson from 2.19.1 to 2.19.2 [ignite-3] via GitHub
  • Re: [PR] Bump jackson from 2.19.1 to 2.19.2 [ignite-3] via GitHub
• [PR] Bump junit5 from 5.13.3 to 5.13.4 [ignite-3] via GitHub
  • Re: [PR] Bump junit5 from 5.13.3 to 5.13.4 [ignite-3] via GitHub
• [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
  • Re: [PR] [MINOR] Minify binary context methods visibility [ignite] via GitHub
• [PR] IGNITE-25862 Fix event log configuration compatibility [ignite-3] via GitHub
  • Re: [PR] IGNITE-25862 Fix event log configuration compatibility [ignite-3] via GitHub
• [PR] IGNITE-25533 Remove Message#onAckReceived [ignite] via GitHub
  • Re: [PR] IGNITE-25533 Remove Message#onAckReceived [ignite] via GitHub
  • Re: [PR] IGNITE-25533 Remove Message#onAckReceived [ignite] via GitHub
  • Re: [PR] IGNITE-25533 Remove Message#onAckReceived [ignite] via GitHub
  • Re: [PR] IGNITE-25533 Remove Message#onAckReceived [ignite] via GitHub
• [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
  • Re: [PR] IGNITE-21899 added GridInt utils [ignite-teamcity-bot] via GitHub
• [PR] IGNITE-25831 Add enums support to OpenAPI test [ignite-3] via GitHub
  • Re: [PR] IGNITE-25831 Add enums support to OpenAPI test [ignite-3] via GitHub
• [PR] IGNITE-25977 Sql. Query optimizer hangs while preparing UNION with huge number of tables [ignite-3] via GitHub
  • Re: [PR] IGNITE-25977 Sql. Query optimizer hangs while preparing UNION with huge number of tables [ignite-3] via GitHub
• [PR] [MINOR] Use ${groupId} instead of explicit group name [ignite] via GitHub
  • Re: [PR] [MINOR] Use ${groupId} instead of explicit group name [ignite] via GitHub
  • Re: [PR] [MINOR] Use ${groupId} instead of explicit group name [ignite] via GitHub
• [PR] IGNITE-25976 Introduce product version comparison [ignite-3] via GitHub
  • Re: [PR] IGNITE-25976 Introduce product version comparison [ignite-3] via GitHub
  • Re: [PR] IGNITE-25976 Introduce product version comparison [ignite-3] via GitHub
  • Re: [PR] IGNITE-25976 Introduce product version comparison [ignite-3] via GitHub
  • Re: [PR] IGNITE-25976 Introduce product version comparison [ignite-3] via GitHub
• [PR] IGNITE-25133 .NET: Include compute executor binaries in release packages [ignite-3] via GitHub
  • Re: [PR] IGNITE-25133 .NET: Include compute executor binaries in release packages [ignite-3] via GitHub
  • Re: [PR] IGNITE-25133 .NET: Include compute executor binaries in release packages [ignite-3] via GitHub
• Re: [PR] IGNITE-25605 Add a mechanism to disable default storage profiles in integration cluster tests [ignite-3] via GitHub
• [PR] IGNITE-25971 Use MessageSerializer for GridQueryKillRequest and GridQueryKillResponse [ignite] via GitHub
  • Re: [PR] IGNITE-25971 Use MessageSerializer for GridQueryKillRequest and GridQueryKillResponse [ignite] via GitHub
  • Re: [PR] IGNITE-25971 Use MessageSerializer for GridQueryKillRequest and GridQueryKillResponse [ignite] via GitHub
• [PR] IGNITE-25970 Use MessageSerializer for MissingMappingRequestMessage and MissingMappingResponseMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25970 Use MessageSerializer for MissingMappingRequestMessage and MissingMappingResponseMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25970 Use MessageSerializer for MissingMappingRequestMessage and MissingMappingResponseMessage [ignite] via GitHub
• [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
  • Re: [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
  • Re: [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
  • Re: [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
  • Re: [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
  • Re: [PR] IGNITE-25768 Sql. Invalid search boundaries are generated when accessing the index if the key is out of range [ignite-3] via GitHub
• [PR] IGNITE-25969 Use MessageSerializer for WalStateAckMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25969 Use MessageSerializer for WalStateAckMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25969 Use MessageSerializer for WalStateAckMessage [ignite] via GitHub
• [PR] IGNITE-25968 Refactor FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Refactor FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Refactor FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
  • Re: [PR] IGNITE-25968 Use MessageSerializer for FragmentDescription [ignite] via GitHub
• [PR] IGNITE-25965 Refactor TxLock message [ignite] via GitHub
  • Re: [PR] IGNITE-25965 Refactor TxLock message [ignite] via GitHub
  • Re: [PR] IGNITE-25965 Refactor TxLock message [ignite] via GitHub
• [PR] IGNITE-25963 Refactor GridCacheMessage message [ignite] via GitHub
  • Re: [PR] IGNITE-25963 Refactor GridCacheMessage message [ignite] via GitHub
  • Re: [PR] IGNITE-25963 Refactor GridCacheMessage message [ignite] via GitHub
  • Re: [PR] IGNITE-25963 Use MessageSerializer for GridCacheMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25963 Use MessageSerializer for GridCacheMessage [ignite] via GitHub
  • Re: [PR] IGNITE-25963 Use MessageSerializer for GridCacheMessage [ignite] via GitHub
• [PR] IGNITE-25961 Refactor GridNearAtomicCheckUpdateRequest message [ignite] via GitHub
  • Re: [PR] IGNITE-25961 IGNITE-25961 Use MessageSerializer for GridCacheIdMessage and GridNearAtomicCheckUpdateRequest [ignite] via GitHub
  • Re: [PR] IGNITE-25961 Use MessageSerializer for GridNearAtomicUpdateResponse and GridNearAtomicCheckUpdateRequest [ignite] via GitHub

• Earlier messages
• Later messages