deepset-ai/haystack
1
0
Fork 0
mirror of https://github.com/deepset-ai/haystack.git synced 2026-10-12 02:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: use random store keys in ToolResultOffloadCompactor reference example

Browse Source
This commit is contained in:
Sebastian Husch Lee
2026-10-09 14:18:37 +02:00
parent b452211bca
commit 9256751714
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs-website/docs/pipeline-components/agents-1/compaction/tool-result-offload-compactor.mdx
+2 -2
View File
@@ -85,8 +85,8 @@ Every part of a result goes to its own store entry, and the reference left in th
```
Tool result offloaded to 2 files:
1. text (4120 characters) at '/abs/path/tool_results/compacted_fetch_call-123_0.txt'. Preview: Quarterly report...
2. image/png (48210 bytes) at '/abs/path/tool_results/compacted_fetch_call-123_1.png'
1. text (4120 characters) at '/abs/path/tool_results/compacted_fetch_9b1c4e7a0d2f4c6b8e1a3d5f7b9c2e4a_0.txt'. Preview: Quarterly report...
2. image/png (48210 bytes) at '/abs/path/tool_results/compacted_fetch_9b1c4e7a0d2f4c6b8e1a3d5f7b9c2e4a_1.png'
```
Image and file content is only written to a store that sets `supports_binary_content`, which [`FileSystemToolResultStore`](../tool-result-offloading.mdx#stores) does. With a text-only store, a result carrying images or files stays in the conversation and a warning is logged.