[GitHub] [skywalking-banyandb] lujiajing1126 commented on pull request #5: Feat: query module

[GitBox <gi...@apache.org>]

lujiajing1126 commented on pull request #5:
URL: https://github.com/apache/skywalking-banyandb/pull/5#issuecomment-860367865


   > From my perspective, the logical plan can't determine which indices should be used, which causes we can't optimize the logical plan before transferring it to physical plans. The reason is we don't support the composited index. A field doesn't exist in more than one index rule, which causes the logical plan doesn't have to select a better rule in a collection. In another word, field criteria separate from each other. I didn't find any paths to do optimization in current step.
   
   So as I understood, in our scenario, the indexed to be used is determinant which does not need further optimization, at least for now, right?
   
   A DAG is hard to be optimized. If we need, we might be better to have a hierarchical structure as a logical plann.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org