LangChain ParentDocumentRetriever: Strike a Balance between large vs small chunks | ClusteredBytes
clusteredbytes.pages.dev · 891 words · saved by 1 readers
Looking at LangChain ParentDocumentRetriever to strike a balance between large vs small document chunks while retrieving related documents.
Table of Contents Small vs Large Document chunks ParentDocumentRetriever Two splitters instead of one Storing both larger and smaller chunks Create the ParentDocumentRetriever Adding the documents Retrieving relevant documents Small vs Large Document chunks # For Retrieval Augmented Generation (RAG), we split the raw text into multiple chunks and embed them using an embedding model (e.g. OpenAI Embeddings). Then we use a retriever to retrieve the most relevant chunks to user's query and feed them chunks to the LLM alongside the input. But what should be the ideal length of each chunk? What's t
saved by
related reading
- LongLLMLingua Prompt Compression Guide | LlamaIndexblog.llamaindex.ai
- Advanced Retriever Techniques to Improve Your RAGs | Towards Data Sciencetowardsdatascience.com
- RAG Chunk Size Guide: Find The Best Setting | LlamaIndexblog.llamaindex.ai
- Building A RAG Pipeline for Semi-structured Data with Langchain - Analytics Vidhyaanalyticsvidhya.com
- Rerankers and Two-Stage Retrieval | Pineconepinecone.io
- Code a simple RAG from scratchhuggingface.co
- The Problem With LangChain | Max Woolf's Blogminimaxir.com
- Towards Data Sciencetowardsdatascience.com
- Summarize Podcast Transcripts and Long Texts Better with NLP and AI | Towards Data Sciencetowardsdatascience.com
- Beyond embeddings: Navigating the shift to completions-only RAGsensible.so
- Advanced RAG Techniques: What They Are & How to Use Themfalkordb.com
- Building Enterprise AI: Hard-Won Lessons from 1200+ Hours of RAG Developmentbytevagabond.com