0Pricing
Vector Databases: Pinecone, Weaviate & pgvector · 강의

질의 변환 기법

벡터 데이터베이스에서 더 효과적으로 검색할 수 있도록 사용자 질의를 바꾸어 쓰거나 확장하는 방법을 살펴봅니다.

질의 변환 기법은(는) CoddyKit의 무료 Vector Databases: Pinecone, Weaviate & pgvector 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Vector Databases: Pinecone, Weaviate & pgvector 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Vector Databases: Pinecone, Weaviate & pgvector 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

What's Query Transformation?

In Retrieval Augmented Generation (RAG), the quality of the information retrieved from your vector database directly impacts the LLM's response. Sometimes, the raw user query isn't ideal for retrieval.

Query transformation is the process of modifying a user's original query to make it more effective for searching your vector database.

Why Original Queries Fall Short

User queries can be:

  • Too short or vague: Lacking enough detail for precise retrieval.
  • Ambiguous: Open to multiple interpretations.
  • Colloquial: Using informal language that doesn't match document embeddings.
  • Complex: Asking multiple questions at once.

These issues lead to irrelevant context being retrieved, impacting RAG quality.

Bridging the Semantic Gap

Your vector database stores information as numerical vectors (embeddings). For effective retrieval, the query's embedding needs to be semantically similar to the embeddings of relevant documents.

Query transformation helps by:

  • Adding more context.
  • Clarifying intent.
  • Aligning query terms with document vocabulary.

This "bridges the semantic gap" for better matches.

Technique 1: Query Expansion

Query expansion involves adding more terms or phrases to the original query. This makes the search broader and increases the chances of hitting relevant documents.

Common methods include:

  • Adding synonyms.
  • Including related concepts.
  • Using domain-specific jargon.

This technique is especially useful for short, vague queries.

Simple Keyword Expansion

Here's a basic Python example where we manually expand a query with related terms. In real systems, an LLM might generate these expansions automatically.

def expand_query_keywords(query):
    expansion_map = {
        "AI": ["artificial intelligence", "machine learning", "deep learning"],
        "vector DB": ["vector database", "embedding store", "Pinecone", "Weaviate"]
    }
    expanded_terms = []
    for keyword, additions in expansion_map.items():
        if keyword.lower() in query.lower():
            expanded_terms.extend(additions)
    
    return query + " " + " ".join(expanded_terms)

# Example usage
user_query = "What is AI?"
transformed_query = expand_query_keywords(user_query)
print(f"Original: {user_query}")
print(f"Transformed: {transformed_query}")

Technique 2: Query Rewriting/Rephrasing

Query rewriting (or rephrasing) uses an LLM to generate a completely new query that is clearer, more specific, or better aligned with the expected content of your documents.

This is particularly effective for:

  • Ambiguous questions.
  • Conversational queries.
  • Queries that implicitly refer to past turns in a conversation.

Rewriting with an LLM

This Python snippet demonstrates how you might use an LLM to rephrase a user query. In a real application, llm_api_call would interact with models like OpenAI GPT or a local LLM.

import os

# Placeholder for an actual LLM API call
def llm_api_call(prompt):
    # For demonstration, we'll simulate a response.
    if "rephrase" in prompt.lower() and "vector databases" in prompt.lower():
        return "Explain the core components and function of vector databases."
    return "Could not rephrase query effectively."

def rephrase_query_with_llm(original_query):
    prompt = f"Rephrase the following user query to be more effective for searching a technical documentation database about vector databases: '{original_query}'"
    rephrased_query = llm_api_call(prompt)
    return rephrased_query

# Example usage
user_query = "Tell me about vector DBs."
transformed_query = rephrase_query_with_llm(user_query)
print(f"Original: {user_query}")
print(f"Transformed: {transformed_query}")

Technique 3: Sub-Query Generation

When a user asks a complex question that involves multiple aspects, a single query might not retrieve all necessary information. Sub-query generation breaks down a complex query into several simpler, more focused queries.

Each sub-query can then be used to retrieve specific pieces of context, which are then combined for the LLM.

Generating Sub-Queries

Here's a conceptual Python example for generating sub-queries. An LLM is often used to parse the original query and identify distinct questions.

import os

# Placeholder for an actual LLM API call
def llm_api_call_sub_query(prompt):
    if "break down" in prompt.lower() and "Pinecone" in prompt.lower():
        return ["What is Pinecone?", "How do I upsert data into Pinecone?", "What is a Pinecone index?"]
    return ["Could not break down query."]

def generate_sub_queries(original_query):
    prompt = f"Break down the following complex user query into a list of simpler, distinct questions for retrieving information from a vector database: '{original_query}'"
    sub_queries = llm_api_call_sub_query(prompt)
    return sub_queries

# Example usage
user_query = "How do I use Pinecone for storing and querying embeddings?"
transformed_queries = generate_sub_queries(user_query)
print(f"Original: {user_query}")
print(f"Sub-queries: {transformed_queries}")

Hybrid & Contextual Transformations

Effective RAG often combines these techniques. You might first rephrase a query, then expand it. Also, consider the conversational context.

  • Multi-turn awareness: Use previous turns to enrich the current query.
  • Hybrid approaches: Combine transformations with traditional keyword search.

Experimentation is key to finding what works best for your data!

Understanding Query Transformation

Which of the following scenarios would MOST benefit from using query expansion as a transformation technique?

Recap: Transforming Queries

You've learned that query transformation is crucial for improving RAG performance by making user queries more effective for vector database retrieval.

  • Query Expansion: Adds terms to broaden search.
  • Query Rewriting: Rephrases for clarity and specificity.
  • Sub-Query Generation: Breaks down complex queries.

Mastering these techniques will significantly enhance the quality of your RAG applications!

자주 묻는 질문

“질의 변환 기법” 강의는 무료인가요?

네 — “질의 변환 기법” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vector Databases: Pinecone, Weaviate & pgvector 강의 전체를 잠금 해제할 수 있습니다. Vector Databases: Pinecone, Weaviate & pgvector 강의에는 총 4개의 강의가 포함되어 있습니다.

“질의 변환 기법”에서 뭘 배우나요?

벡터 데이터베이스에서 더 효과적으로 검색할 수 있도록 사용자 질의를 바꾸어 쓰거나 확장하는 방법을 살펴봅니다. 브라우저에서 직접 실행하는 실습 코드로 Vector Databases: Pinecone, Weaviate & pgvector을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Vector Databases: Pinecone, Weaviate & pgvector을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Vector Databases: Pinecone, Weaviate & pgvector은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“질의 변환 기법” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Vector Databases: Pinecone, Weaviate & pgvector 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Vector Databases: Pinecone, Weaviate & pgvector 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. 질의 변환 기법
  2. 다단계 RAG 파이프라인
  3. RAG 시스템 성능 평가
  4. 검색 결과 재순위화
← Vector Databases: Pinecone, Weaviate & pgvector(으)로 돌아가기