Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
TcpDiscoverySslSelfTest.testFailedNodes3
https://ci2.ignite.apache.org/test/-2830914425109362780?currentProjectId=IgniteTests24Java8&branch=%3Cdef
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
CacheAffinityCallSelfTest.testAffinityCallFromClientRestartNode
https://ci2.ignite.apache.org/test/-1518884284898819236?currentProjectId=IgniteTes
Hello, Nikolay,
as far as I know, the following paper usually referred as a part of
original inspiration:
https://www.csd.uoc.gr/~hy460/pdf/p650-lehman.pdf
I also heard rumors that the code was partially inspired by the PostgreSQL
implementation.
I don't know any other sources except for the cod
Hi Nikolay,
Send a note to Sergi who implemented the tree for Ignite:
https://www.linkedin.com/in/sergi-vladykin-a4781536/
--
Denis
On Tue, Jul 19, 2022 at 9:42 AM Николай Ижиков wrote:
> Hello, Igniters and espesially Ignite veterans.
>
>
> While study Ignite B+ tree I’m wondering - what was
Hello, Igniters and espesially Ignite veterans.
While study Ignite B+ tree I’m wondering - what was initial design of this data
structure?
Is it based on some paper or inspired by some existing implementation?
What should I study beside source code to better understand Ignite b+ tree and
how it
