Problemsby GlyphLlamaIndex vector search quality is hard to get right
2 posts from 2 people2d activeSteady, +1 this weekunverified
Posts per day
The posts behind it
[Bug]: RecursiveRetriever retains lower-scoring duplicates depending on traversal order
### Bug Description ### Description `RecursiveRetriever` deduplicates results by node ID but always retains the first occurrence, even when a later retrieval path returns the same node with a higher score. The `_deduplicate_nodes()` docstring mentions retaining the...
[Feature Request]: Add autoEmbed vector search and reranker stage to MongoDBAtlasVectorSearch
### Feature Description Add the new capabilities of autoEmbed from vector search and the reranker native stage to MongoDBAtlasVectorSearch ### Reason The current version of MongoDBAtlasVectorSearch does not allow for autoEmbed or add the native reranker stage ### Value of...
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 43 days. Mostly on run-llama/llama_index.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "vector-search" rule about LlamaIndex. First post Sep 11, 2026, latest Oct 23, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Vector search quality and scaling are hard to get right
10 posts from 10 people on GitHub issues, Reddit, Hacker News.
Qdrant vector search quality is hard to get right
9 posts from 8 people on GitHub issues.
Claude Code vector search quality is hard to get right
2 posts from 2 people on GitHub issues. Unverified.
Databricks vector search quality is hard to get right
2 posts from 2 people on Reddit. Unverified.
Oracle vector search quality is hard to get right
2 posts from 2 people on GitHub issues. Unverified.
Pinecone vector search quality is hard to get right
2 posts from 1 person on GitHub issues. Unverified.
Other LlamaIndex problems
LlamaIndex upgrades break working setups
17 posts from 10 people on GitHub issues.
LlamaIndex users keep filing bugs
Top post: "FunctionTool wraps a returned ToolOutput as a success and drops is_error", one of 16 posts from 13 people on GitHub issues, Stack Overflow.
LlamaIndex fails to return valid structured output
5 posts from 5 people on GitHub issues.
RAG on LlamaIndex returns irrelevant or missing context
3 posts from 3 people on GitHub issues.
LlamaIndex lock-in makes switching costly
3 posts from 3 people on GitHub issues.
Trouble with LlamaIndex returns
Top post: "LegacyOfficeReader returns a Document with text None for a document with no text", one of 3 posts from 3 people on GitHub issues.
Trouble with LlamaIndex documents
Top post: "MoorchehVectorStore sparse-vector path raises NameError (missing imports, undefined 'documents', ImpotError", one of 3 posts from 3 people on GitHub issues.
Experiments on LlamaIndex are hard to reproduce and track
3 posts from 3 people on GitHub issues.
Trouble with LlamaIndex events
Top post: "CBEvent assigns generated uuid to self.id instead of self.id_, so events without an id all share id_=", one of 3 posts from 3 people on GitHub issues.
LlamaIndex integrations break or are missing
2 posts from 2 people on GitHub issues. Unverified.
LlamaIndex runs out of context on real work
2 posts from 1 person on GitHub issues. Unverified.
LlamaIndex token costs are hard to predict
2 posts from 2 people on GitHub issues. Unverified.
History