---
title: "Most \"Graph RAG\" implementations are vector retrieval with extra steps.\n\n@datagraphs built something..."
source_name: "Qdrant(@qdrant_engine)"
original_url: "https://x.com/qdrant_engine/status/2050227127472337345"
canonical_url: "https://www.traeai.com/articles/33d94d72-41b6-4a9d-af89-2d264192cb71"
content_type: "tweet"
language: "中文"
score: 8.7
tags: ["RAG","Graph Database","Vector Search","Qdrant","Knowledge Graph"]
published_at: "2026-05-01T14:53:33+00:00"
created_at: "2026-05-02T10:53:51.76967+00:00"
---

# Most "Graph RAG" implementations are vector retrieval with extra steps.

@datagraphs built something...

Canonical URL: https://www.traeai.com/articles/33d94d72-41b6-4a9d-af89-2d264192cb71
Original source: https://x.com/qdrant_engine/status/2050227127472337345

## Summary

Qdrant 指出多数“图RAG”实为套壳向量检索，而 @datagraphs 构建了真正融合图数据库与向量搜索的协同架构：通过 schema-first agent 调度并行图查与语义检索，实现可验证、低延迟、全栈可控的知识问答。

## Key Takeaways

- 图与向量非互斥，而是互补：图擅精确逻辑查询（否定/时间/计算），向量擅语义相似匹配
- 真实图RAG需schema感知agent调度、实时图嵌入同步、图/向量并行检索与结果融合
- Qdrant被选中主因是混合云部署能力、payload过滤DSL兼容性及Terraform原生支持

## Content

Title: Qdrant on X: "Most "Graph RAG" implementations are vector retrieval with extra steps.

@datagraphs built something different.

Their UK-based knowledge graph platform combines a proprietary graph database engine with Qdrant-powered semantic search, orchestrated by an agentic layer that picks https://t.co/eg5Zb2mDl8" / X

URL Source: http://x.com/qdrant_engine/status/2050227127472337345

Markdown Content:
Most "Graph RAG" implementations are vector retrieval with extra steps.

built something different. Their UK-based knowledge graph platform combines a proprietary graph database engine with Qdrant-powered semantic search, orchestrated by an agentic layer that picks the right retrieval path for each prompt. The insight from CEO Paul Wilton: vector and graph aren't competitors. They're complementary. Vector excels at semantic similarity over unstructured content. Graphs excel at empirical queries: negation, date ranges, mathematical operations on connected data. Force one to do the other's job and the system breaks. What they built: - Real-time embedding from the graph into Qdrant collections via streaming and queuing - Schema-first retrieval where the agent pulls the full graph schema before deciding how to query - Parallel execution across graph queries and vector retrieval, blended for the LLM - Every answer cited back to source for verifiable provenance Why Qdrant specifically: - Hybrid Cloud kept the entire stack inside their own AWS environment - Payload filtering DSL closely matched their existing OpenSearch patterns, so common metadata structures worked across the graph, OpenSearch, and Qdrant without translation - Terraform support and infrastructure automation fit their existing CI/CD workflows 18 months in production. Zero significant issues. The retrieval layer determines the ceiling of your AI's intelligence. Choose the right components. Compose them well. Full case study: [qdrant.tech/blog/case-stud](https://t.co/ffyuxltK9b)