0Pricing
Vector Databases: Pinecone, Weaviate & pgvector · Aula

Técnicas de Transformação de Consultas

Explore métodos para reformular ou expandir consultas de usuários e obter uma recuperação mais eficaz no banco de dados vetorial.

Técnicas de Transformação de Consultas é uma aula grátis de Vector Databases: Pinecone, Weaviate & pgvector no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Vector Databases: Pinecone, Weaviate & pgvector, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Vector Databases: Pinecone, Weaviate & pgvector inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

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!

Perguntas Frequentes

A aula “Técnicas de Transformação de Consultas” é grátis?

Sim — o texto completo de “Técnicas de Transformação de Consultas” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Vector Databases: Pinecone, Weaviate & pgvector, atualize para CoddyKit PRO. O curso de Vector Databases: Pinecone, Weaviate & pgvector inclui 4 aulas no total.

O que vou aprender em “Técnicas de Transformação de Consultas”?

Explore métodos para reformular ou expandir consultas de usuários e obter uma recuperação mais eficaz no banco de dados vetorial. Você pratica Vector Databases: Pinecone, Weaviate & pgvector com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Vector Databases: Pinecone, Weaviate & pgvector?

Nenhuma experiência prévia é necessária. Vector Databases: Pinecone, Weaviate & pgvector no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Técnicas de Transformação de Consultas”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Vector Databases: Pinecone, Weaviate & pgvector?

Sim. Cada aula de Vector Databases: Pinecone, Weaviate & pgvector inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Técnicas de Transformação de Consultas
  2. Pipelines RAG em Múltiplas Etapas
  3. Avaliando o Desempenho de Sistemas RAG
  4. Reordenando resultados recuperados
← Voltar para Vector Databases: Pinecone, Weaviate & pgvector