notifications  

Messages by Thread

• • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
  • Re: [PR] IGNITE-22141 C++ 3.0: Implement Partition Awareness for C++ client [ignite-3] via GitHub
• [PR] IGNITE-28503 Add sitemap generation script and update sitemap [ignite-website] via GitHub
  • Re: [PR] IGNITE-28503 Add sitemap generation script and update sitemap [ignite-website] via GitHub
• [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
  • Re: [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
  • Re: [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
  • Re: [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
  • Re: [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
  • Re: [PR] IGNITE-28502 Calcite SQL: Add deadlock detection for queries initiated by UDF [ignite] via GitHub
• Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
  • Re: [PR] IGNITE-27685 Implement exponential backoff for durable finish [ignite-3] via GitHub
• [PR] Bump io.swagger.core.v3:swagger-annotations from 2.2.46 to 2.2.47 [ignite-3] via GitHub
  • Re: [PR] Bump io.swagger.core.v3:swagger-annotations from 2.2.46 to 2.2.47 [ignite-3] via GitHub
  • Re: [PR] Bump io.swagger.core.v3:swagger-annotations from 2.2.46 to 2.2.47 [ignite-3] via GitHub
• [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
  • Re: [PR] IGNITE-28501 Retry channel open attempt in most cases [ignite-3] via GitHub
• [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
  • Re: [PR] IGNITE-28221 : combining of the message factories v2 [ignite] via GitHub
• (ignite-website) branch master updated: IGNITE-28500 Add redirection for downloads page (#330) ptupitsyn
• Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
  • Re: [PR] IGNITE-27678 Same partitions on different nodes can hold different updates if writeThrough is enabled [ignite] via GitHub
• [PR] IGNITE-28500 Add redirection for downloads page [ignite-website] via GitHub
  • Re: [PR] IGNITE-28500 Add redirection for downloads page [ignite-website] via GitHub
• [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
  • Re: [PR] IGNITE-28475 Document CacheInterceptor interaction with keepBinary cache wrapper [ignite] via GitHub
• Re: [PR] Debug Disco SSL ciphers [ignite] via GitHub
• [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28308 Remove Serializable from discovery custom messages [ignite] via GitHub
• [PR] IGNITE-28496 remove pageAcquireTime metric due to perf loss [ignite-3] via GitHub
  • Re: [PR] IGNITE-28496 remove pageAcquireTime metric due to perf loss [ignite-3] via GitHub
• [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Remove Serializable from Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Use MessageSerializer for Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Use MessageSerializer for Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Use MessageSerializer for Zookeeper discovery custom messages [ignite] via GitHub
  • Re: [PR] IGNITE-28498 Use MessageSerializer for Zookeeper discovery custom messages [ignite] via GitHub
• [PR] IGNITE-28497 Revert ErrorGroups removal [ignite-3] via GitHub
  • Re: [PR] IGNITE-28497 Revert file transfer ErrorGroups removal [ignite-3] via GitHub
• [PR] IGNITE-25974 C++ tests do not catch unsynced changes to ErrorGroups.java [ignite-3] via GitHub
  • Re: [PR] IGNITE-25974 Verify platform ErrorGroups generation [ignite-3] via GitHub
• Re: [PR] IGNITE-28469 Sql. Partition pruning doesn't work for temporal types and dynamic params [ignite-3] via GitHub
• [PR] IGNITE-28493 Reduce contention in RemotelyTriggeredResourceRegistry [ignite-3] via GitHub
  • Re: [PR] IGNITE-28493 Reduce contention in RemotelyTriggeredResourceRegistry [ignite-3] via GitHub
• [PR] IGNITE-28459 Fixed unhandled NIO Session Requests during node stop [ignite] via GitHub
  • Re: [PR] IGNITE-28459 Fixed unhandled NIO Session Requests during node stop [ignite] via GitHub
  • Re: [PR] IGNITE-28459 Fixed unhandled NIO Session Requests during node stop [ignite] via GitHub
• (ignite-website) branch master updated: IGNITE-28491 Restore missing js file for legacy download page (#329) ptupitsyn
• Re: [PR] IGNITE-28036 Fix flaky IgniteOfflineBaselineNodeFullApiSelfTest [ignite] via GitHub
  • Re: [PR] IGNITE-28036 Fix flaky IgniteOfflineBaselineNodeFullApiSelfTest [ignite] via GitHub
• [PR] IGNITE-28489 GridNearTxLocal leaks thread state on transaction timeout during initialization [ignite] via GitHub
  • Re: [PR] IGNITE-28489 GridNearTxLocal leaks thread state on transaction timeout during initialization [ignite] via GitHub
  • Re: [PR] IGNITE-28489 GridNearTxLocal leaks thread state on transaction timeout during initialization [ignite] via GitHub
  • Re: [PR] IGNITE-28489 GridNearTxLocal leaks thread state on transaction timeout during initialization [ignite] via GitHub
  • Re: [PR] IGNITE-28489 GridNearTxLocal leaks thread state on transaction timeout during initialization [ignite] via GitHub
• [PR] IGNITE-28389 SQL. Eliminate table scans with always_false predicate. [ignite-3] via GitHub
  • Re: [PR] IGNITE-28389 SQL. Eliminate table scans with always_false predicate [ignite-3] via GitHub
  • Re: [PR] IGNITE-28389 SQL. Eliminate table scans with always_false predicate [ignite-3] via GitHub
• [PR] IGNITE-28490 Add redirection for downloads page [ignite-website] via GitHub
  • Re: [PR] IGNITE-28490 Add redirection for downloads page [ignite-website] via GitHub
  • [PR] IGNITE-28490 Add redirection for downloads page [ignite-website] via GitHub
  • Re: [PR] IGNITE-28490 Add redirection for downloads page [ignite-website] via GitHub
• [PR] IGNITE-28491 Add missing js file [ignite-website] via GitHub
  • Re: [PR] IGNITE-28491 Restore missing js file for legacy download page [ignite-website] via GitHub
• (ignite-website) branch master updated: IGNITE-28490 Add redirection for downloads page (#328) ptupitsyn
• [PR] IGNITE-27926 Implement Raft group destruction in Segstore [ignite-3] via GitHub
  • Re: [PR] IGNITE-27926 Implement Raft group destruction in Segstore [ignite-3] via GitHub
  • Re: [PR] IGNITE-27926 Implement Raft group destruction in Segstore [ignite-3] via GitHub
  • Re: [PR] IGNITE-27926 Implement Raft group destruction in Segstore [ignite-3] via GitHub
  • Re: [PR] IGNITE-27926 Implement Raft group destruction in Segstore [ignite-3] via GitHub
• [PR] Bump jline from 4.0.10 to 4.0.12 [ignite-3] via GitHub
  • Re: [PR] Bump jline from 4.0.10 to 4.0.12 [ignite-3] via GitHub
• Re: [PR] IGNITE-28456 Fix race in NodeImpl.init() causing double electSelf() for single-node Raft groups [ignite-3] via GitHub
• Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
  • Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
  • Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
  • Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
  • Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
  • Re: [PR] IGNITE-28259 Remove IgniteDhtPartitionHistorySuppliersMap [ignite] via GitHub
• [PR] IGNITE-28408 Add Ignite version logging [ignite-extensions] via GitHub
  • Re: [PR] IGNITE-28408 PerfStat: Add Ignite version logging [ignite-extensions] via GitHub

• Earlier messages
• Later messages