>
>
> Since I am currently familiarizing myself with the system's internal
> design, I would welcome any suggestions on specific areas of the
> documentation or codebase I should prioritize to better understand the
> current search logic :)
>

I think starting with the unit tests in a module you’re interested in would
be a good way to understand the design and functionality. Some components
run in parallel, so using a debugger and taking thread dumps can help
there. This is what helped me when I was getting set up a few years ago 🙂.
There are also some research papers, especially this one:
https://asterix.ics.uci.edu/pub/Hyracks.pdf (intro and design sections)

Reply via email to