The community member is building a composable graph to modularly add or remove indices, but is having trouble with the "tree_summarize" feature. Another community member suggests that "tree_summarize" can be passed as an argument to the indexes in the graph, and that the composable graph routes queries to specific indexes using the settings from the query configs. However, the original community member is unsure if this is documented and wants to confirm. There is also a discussion around what happens if two List Indices have the information needed to answer a query, with a suggestion that the response mode can be set in the query config to handle this. The community members also discuss passing a separate dict for query configs rather than using kwargs directly, and one community member suggests checking out a guide on composability in the GPT-Index documentation.
I'm building a composable graph as a hamfisted attempt to modularly add or remove indices.
ComposableGraph doesn't let me do things like "tree_summarize" what traversals exist for that? I would be open to using a different means of composing indices.
You can pass tree_summarize as an argument to the indexes in the graph
All the composable graph does is route your queries to specific indexes, and then those indexes are queried using the settings from the query configs π