Hello! I am currently experimenting with Decompose query transform on a graph structure (a vector index of vectors subindices). However, the current DEFAULT_DECOMPOSE_QUERY_TRANSFORM_TMP doesnt seem to accurately decompose my original query. Is it possible for a me to create/edit the DEFAULT_DECOMPOSE_QUERY_TRANSFORM_TMP without breaking the current code?
Hello! I just had a question about how composability works under the hood. My use case is as follows I have there docs as vector stores:- index1 = GPTSimpleVectorIndex.from_documents(doc1) index2 = GPTSimpleVectorIndex.from_documents(doc2) index3 = GPTSimpleVectorIndex.from_documents(doc3)
I then created a list index and further transformed it into a graph:- graph = ComposableGraph.build_from_indices( GPTListIndex, [index1, index2, index3], index_summaries=[index1_summary, index2_summary, index3_summary], )
My queries involve a mixture of questions such as querying individual docs (eg. summarise doc1), compare/contrast between pairs or triplets, etc
I was just wondering if there are any specific query_config I need to use and how exactly it works to address the above query use cases?
