Find answers from the community

Updated 2 weeks ago

LLMs for Advanced Question-Answering ove...

Hi everyone,
I had the chance to watch this great video by Jerry (https://www.youtube.com/watch?v=L1o1VPVfbb0) and although Query Pipelines are now depricated and now replaced with Workflows, the same notebook has been updated with Workflows here (https://docs.llamaindex.ai/en/stable/examples/workflow/advanced_text_to_sql/) however, here is the catch:
  1. I tried to use Arize Pheonix to trace the execution of the last workflow and what I got was separate record for each step in the Workflow, not nested or linked together.
  2. There is a class called "NLSQLTableQueryEngine" which implements the first Workflow in the previous notebook, this one doesn't use Workflows and is tracked very well on Arize Pheonix.
So I wonder if the complete query-time row retrieved implementation can be implemented as a traceable class like "NLSQLTableQueryEngine" or if the Workflow can be traced using Arize Pheonix.

TBH, it's hard to read the source code and understand how everything works (I tried) to answer this question myself.
L
O
4 comments
what version of llama-index / arize did you use? The steps in the workflow should all be nested under the same Workflow.run() in arize πŸ‘€
The llama_index version I'm using is 0.11.22, and I attached is the output I get from Pheonix (open-source, docker image, version: latest).
Attachment
image.png
And when I click on the Workflow.run record, this is what I get:
Attachment
image.png
could be a version issue tbh, but let me try to reproduce with latest
Add a reply
Sign up and join the conversation on Discord