Add genie tool support and add the trace details in databricks mlflow tracing #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Items:
It is implemented by creating two nested tool calls to simulate invoking a tool to be picked up by databricks tracing. This lets you only expose query results to the llm but provide a trace for the query description, query and results in the tracing UI. Look at the usage and screenshots below. It uses tool with
response_format: str = "content_and_artifact"
which when invoked will include a trace with the genie tool call and a detailed nested trace right underneath it.You can test in Databricks with the preview enabled via:
AgentExecutor Usage:
LangGraph