When trying to perform queries on

id stay away from composable graph

Use sub question query engine and routers imo

Just be careful, both of those only scale to so many indexes (like 10 or so). If you have more, you might have to introduce a step to filter them down using embeddings

They dont fit my usecase, I was looking for a high scale solution.

I thought that by using a composable graph I might look at each index's summary and select based on those, similary on how SummaryIndex works

Any particular reason for staying away from composable graphs?

The problem of using SubQuestionQueryEngine and RouterQuery engine is that they dont work very well with OpenSource models according to this table: https://docs.llamaindex.ai/en/stable/module_guides/models/llms.html#open-source-llms

they are outdated, unmaintained, and about to be removed

yea thats fair --agentic behaviour is hard

There is an embedding router thats a bit more stable

anything that requires parsing outputs is hard for opensource LLMs

I guess my best option is to associate an embedding to each index and implement a search of those emeddings to retrieve the index

yes -- thats what the embeddings router does actually 🙂

Something like this I think
https://docs.llamaindex.ai/en/stable/examples/query_engine/RetrieverRouterQueryEngine.html

https://docs.llamaindex.ai/en/stable/examples/query_engine/RouterQueryEngine.html this one?

ah

Thats the difference between them?

The one you sent uses embeddings and the one I sent uses LLM

Pretty much 🙂