How to debug source code of Milvus to understand the hybrid queries execution path.

[rsrs2013]

Hello Community,

I am trying to understand the milvus source code, especially the part of how search happens for a hybrid query. I found this discussion by @yhmo very useful link. It gave some starting point.

Now I am trying to go further and see how a hybrid query gets executed by using some LOG_INFO statements. I am having the following doubts:

1. From the SegmentInternalInterface::Search in the segcore/segment_interface.cpp file, the control goes to the get_moved_result(PlanNode& node) function in the ExecPlanNodeVisitor.h. And here the node.accept, virtual function is called based on the PlanNode type. So how to introduce LOG_INFO in the ExecPlanNodeVisitor.h ? This is because, it is a generated file. So it says Don't edit the code.
2. Who creates the PlanNode and how to know the type of the PlanNode created while debugging ?
3. What is the way I need to debug to understand how hybrid queries are executed in Milvus

-Thanks in advance.

[xiaofan-luan]

hi rs,
PlanNode is actually created from golang side

When you do hybridSearch, start from
impl.go at proxy. HybridSearch
then you check task.search
parser is where PlanNode generated

Then on querynodes
Search -> SearchChannel -> SearchSegments and then you step into cgo calls