0Pricing
LangChain / RAG / Vector DBs · 课时

使用自定义逻辑扩展检索链

构建自定义检索链,集成复杂的业务逻辑、预处理步骤或专用筛选功能。

使用自定义逻辑扩展检索链 是 CoddyKit 上的免费 LangChain / RAG / Vector DBs 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 LangChain / RAG / Vector DBs 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 LangChain / RAG / Vector DBs 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Beyond Basic RAG

Welcome! In this lesson, we'll dive into extending LangChain's retrieval chains. While standard Retrieval Augmented Generation (RAG) is powerful, real-world applications often need more nuanced control.

We'll learn how to inject custom logic into the retrieval process to make your RAG systems smarter and more tailored to specific needs.

Practical Customization Needs

Why would you need custom logic in a retrieval chain? Consider these common scenarios:

  • Filtering by User Permissions: Only retrieve documents accessible to the current user.
  • Prioritizing Fresh Data: Boost documents created or updated recently.
  • Removing Irrelevant Sections: Clean up retrieved text before passing it to the LLM.
  • Dynamic Query Rephrasing: Automatically improve user queries for better search results.

These needs go beyond what a basic retriever offers.

LangChain's Custom Primitives

LangChain provides flexible primitives to insert custom Python logic directly into your chains:

  • RunnableLambda: This allows you to wrap any Python function, making it a runnable component. It's perfect for applying arbitrary transformations.
  • RunnablePassthrough: This simply passes its input through to the next step. It's useful for injecting new keys into the input dictionary or for identity operations.

These are your building blocks for custom steps.

Enhancing User Queries (Pre-processing)

One powerful customization is query pre-processing. This means modifying the user's input query before it's sent to the retriever or vector store.

  • You could add specific keywords based on detected intent.
  • Expand common abbreviations or synonyms.
  • Rephrase the query to improve embedding search results.

This subtle step can significantly boost the relevance of retrieved documents.

Custom Query Transformer Code

Let's see how to implement a simple query pre-processor using RunnableLambda. This example adds a 'detailed search for' prefix to the original query.

from langchain_core.runnables import RunnableLambda
from langchain_core.promnpts import ChatPromptTemplate
from langchain_openai import ChatOpenAI

# Mock LLM for demonstration purposes
class MockLLM(ChatOpenAI):
    def invoke(self, input):
        return f"LLM processed: {input['enhanced_query']}"

def enhance_query(input_dict):
    original_query = input_dict["question"]
    return {"enhanced_query": f"detailed search for {original_query}"}

llm = MockLLM() # In a real app, use ChatOpenAI(model="gpt-4")

prompt = ChatPromptTemplate.from_template(
    "Answer based on the following search query: {enhanced_query}"
)

custom_chain = (
    {"enhanced_query": RunnableLambda(enhance_query)} # Our custom step
    | prompt
    | llm
)

result = custom_chain.invoke({"question": "latest AI trends"})
print(result)

Refining Retrieved Documents (Post-processing)

Another crucial area for custom logic is document post-processing. This occurs after documents have been retrieved but before they are passed to the LLM.

  • Filtering: Remove documents that don't meet certain criteria (e.g., outdated, wrong source).
  • Re-ranking: Reorder documents based on custom relevance scores.
  • Summarizing: Condense lengthy documents to fit context windows.

This ensures the LLM receives the most relevant and concise context, improving answer quality and reducing token usage.

Filtering Documents by Metadata

Here's an example of filtering retrieved documents based on their metadata. We'll simulate a retriever that returns documents and then filter them to only include those from a specific 'blog' source.

from langchain_core.documents import Document
from langchain_core.runnables import RunnableLambda
from langchain_core.promnpts import ChatPromptTemplate
from langchain_openai import ChatOpenAI

# Mock LLM for demonstration
class MockLLM(ChatOpenAI):
    def invoke(self, input):
        context = input.get("context", "No context provided")
        return f"LLM processed docs: {context}"

# Mock retriever returning Documents with metadata
def mock_retrieve(query):
    return [
        Document(page_content="Doc A about AI", metadata={"source": "blog"}),
        Document(page_content="Doc B about ML", metadata={"source": "research"}),
        Document(page_content="Doc C about AI ethics", metadata={"source": "blog"}),
    ]

def filter_by_source(docs, desired_source="blog"):
    # Only keep documents from the 'blog' source
    return [doc for doc in docs if doc.metadata.get("source") == desired_source]

llm = MockLLM()
prompt = ChatPromptTemplate.from_template(
    "Answer based on the following context: {context}"
)

# Build a simple chain with retrieval and custom filter
custom_retrieval_chain = (
    RunnableLambda(mock_retrieve) # Simulate retrieval
    | RunnableLambda(filter_by_source) # Apply custom filter
    | (lambda docs: {"context": "\n\n".join([d.page_content for d in docs])}) # Format for LLM
    | prompt
    | llm
)

result = custom_retrieval_chain.invoke("AI topics")
print(result)

End-to-End Custom Chain

You can combine both query pre-processing and document post-processing within a single LangChain chain. The flow would look something like this:

  1. User Query
  2. Custom Query Pre-processor
  3. Retriever (e.g., Vector Store)
  4. Custom Document Post-processor
  5. LLM for Answer Generation

This modular approach gives you fine-grained control over every step of your RAG pipeline, making it highly adaptable to complex requirements.

Advanced: Conditional Routing

For even more dynamic behavior, LangChain offers RunnableBranch. This powerful construct allows your chain to take different paths based on certain conditions.

For example, you could:

  • Use one retriever if the query is about 'code' and another for 'general knowledge'.
  • Apply different document filters based on the user's role.

RunnableBranch enables sophisticated, context-aware RAG workflows.

Check Your Understanding

Which LangChain primitive is best suited for inserting a simple Python function to modify data (e.g., filter a list of documents) within a chain?

Recap: Extending Retrieval

Great job! In this lesson, you learned how to extend LangChain retrieval chains with custom logic:

  • We explored the need for customization in real-world RAG.
  • You discovered RunnableLambda and RunnablePassthrough as key tools.
  • We saw how to pre-process queries for better retrieval.
  • You learned to post-process retrieved documents for refined context.
  • We touched on advanced concepts like RunnableBranch for conditional logic.

Experiment with these techniques to build highly customized and efficient RAG applications!

常见问题解答

「使用自定义逻辑扩展检索链」课时是免费的吗?

是的 — 「使用自定义逻辑扩展检索链」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 LangChain / RAG / Vector DBs 课程的其余内容,请升级到 CoddyKit PRO。 LangChain / RAG / Vector DBs 课程共包含 4 节课。

「使用自定义逻辑扩展检索链」这节课中我会学到什么?

构建自定义检索链,集成复杂的业务逻辑、预处理步骤或专用筛选功能。 你通过在浏览器中直接运行的动手代码来练习 LangChain / RAG / Vector DBs,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 LangChain / RAG / Vector DBs 需要有经验吗?

无需任何先前经验。CoddyKit 上的 LangChain / RAG / Vector DBs 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。

「使用自定义逻辑扩展检索链」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 LangChain / RAG / Vector DBs 课中编写并运行代码吗?

能。每节 LangChain / RAG / Vector DBs 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 开发自定义文档加载器
  2. 集成自定义嵌入模型
  3. 使用自定义逻辑扩展检索链
  4. 构建自定义输出解析器
← 返回 LangChain / RAG / Vector DBs