mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com>
163 lines
6.1 KiB
Plaintext
163 lines
6.1 KiB
Plaintext
---
|
|
title: Busca Vetorial Weaviate
|
|
description: O `WeaviateVectorSearchTool` foi projetado para buscar documentos semanticamente similares em um banco de dados vetorial Weaviate.
|
|
icon: network-wired
|
|
mode: "wide"
|
|
---
|
|
|
|
## Visão Geral
|
|
|
|
O `WeaviateVectorSearchTool` foi especificamente desenvolvido para realizar buscas semânticas em documentos armazenados em um banco de dados vetorial Weaviate. Essa ferramenta permite encontrar documentos semanticamente similares a uma determinada consulta, aproveitando o poder das embeddings vetoriais para resultados de busca mais precisos e contextualmente relevantes.
|
|
|
|
[Weaviate](https://weaviate.io/) é um banco de dados vetorial que armazena e consulta embeddings vetoriais, possibilitando recursos de busca semântica.
|
|
|
|
## Instalação
|
|
|
|
Para incorporar esta ferramenta ao seu projeto, é necessário instalar o cliente Weaviate:
|
|
|
|
```shell
|
|
uv add weaviate-client
|
|
```
|
|
|
|
## Etapas para Começar
|
|
|
|
Para utilizar efetivamente o `WeaviateVectorSearchTool`, siga as etapas abaixo:
|
|
|
|
1. **Instalação dos Pacotes**: Confirme que os pacotes `crewai[tools]` e `weaviate-client` estão instalados em seu ambiente Python.
|
|
2. **Configuração do Weaviate**: Configure um cluster Weaviate. Você pode seguir as instruções na [documentação do Weaviate](https://weaviate.io/developers/wcs/manage-clusters/connect).
|
|
3. **Chaves de API**: Obtenha a URL do seu cluster Weaviate e a chave de API correspondente.
|
|
4. **Chave de API da OpenAI**: Certifique-se de que você tenha uma chave de API da OpenAI definida nas variáveis de ambiente como `OPENAI_API_KEY`.
|
|
|
|
## Exemplo
|
|
|
|
O exemplo a seguir demonstra como inicializar a ferramenta e executar uma busca:
|
|
|
|
```python Code
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
|
|
# Inicializar a ferramenta
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
|
|
@agent
|
|
def search_agent(self) -> Agent:
|
|
'''
|
|
Este agente utiliza o WeaviateVectorSearchTool para buscar
|
|
documentos semanticamente similares em um banco de dados vetorial Weaviate.
|
|
'''
|
|
return Agent(
|
|
config=self.agents_config["search_agent"],
|
|
tools=[tool]
|
|
)
|
|
```
|
|
|
|
## Parâmetros
|
|
|
|
O `WeaviateVectorSearchTool` aceita os seguintes parâmetros:
|
|
|
|
- **collection_name**: Obrigatório. O nome da coleção a ser pesquisada.
|
|
- **weaviate_cluster_url**: Obrigatório. A URL do cluster Weaviate.
|
|
- **weaviate_api_key**: Obrigatório. A chave de API para o cluster Weaviate.
|
|
- **limit**: Opcional. O número de resultados a serem retornados. O padrão é `3`.
|
|
- **vectorizer**: Opcional. O vetorizador a ser utilizado. Se não for informado, será utilizado o `text2vec_openai` com o modelo `nomic-embed-text`.
|
|
- **generative_model**: Opcional. O modelo generativo a ser utilizado. Se não for informado, será utilizado o `gpt-4o` da OpenAI.
|
|
|
|
## Configuração Avançada
|
|
|
|
Você pode personalizar o vetorizador e o modelo generativo utilizados pela ferramenta:
|
|
|
|
```python Code
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
from weaviate.classes.config import Configure
|
|
|
|
# Configurar modelo personalizado para vetorizador e modelo generativo
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
vectorizer=Configure.Vectorizer.text2vec_openai(model="nomic-embed-text"),
|
|
generative_model=Configure.Generative.openai(model="gpt-4o-mini"),
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
```
|
|
|
|
## Pré-carregando Documentos
|
|
|
|
Você pode pré-carregar seu banco de dados Weaviate com documentos antes de utilizar a ferramenta:
|
|
|
|
```python Code
|
|
import os
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
import weaviate
|
|
from weaviate.classes.init import Auth
|
|
|
|
# Conectar ao Weaviate
|
|
client = weaviate.connect_to_weaviate_cloud(
|
|
cluster_url="https://your-weaviate-cluster-url.com",
|
|
auth_credentials=Auth.api_key("your-weaviate-api-key"),
|
|
headers={"X-OpenAI-Api-Key": "your-openai-api-key"}
|
|
)
|
|
|
|
# Obter ou criar coleção
|
|
test_docs = client.collections.get("example_collections")
|
|
if not test_docs:
|
|
test_docs = client.collections.create(
|
|
name="example_collections",
|
|
vectorizer_config=Configure.Vectorizer.text2vec_openai(model="nomic-embed-text"),
|
|
generative_config=Configure.Generative.openai(model="gpt-4o"),
|
|
)
|
|
|
|
# Carregar documentos
|
|
docs_to_load = os.listdir("knowledge")
|
|
with test_docs.batch.dynamic() as batch:
|
|
for d in docs_to_load:
|
|
with open(os.path.join("knowledge", d), "r") as f:
|
|
content = f.read()
|
|
batch.add_object(
|
|
{
|
|
"content": content,
|
|
"year": d.split("_")[0],
|
|
}
|
|
)
|
|
|
|
# Inicializar a ferramenta
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
```
|
|
|
|
## Exemplo de Integração com Agente
|
|
|
|
Veja como integrar o `WeaviateVectorSearchTool` com um agente CrewAI:
|
|
|
|
```python Code
|
|
from crewai import Agent
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
|
|
# Inicializar a ferramenta
|
|
weaviate_tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
|
|
# Criar um agente com a ferramenta
|
|
rag_agent = Agent(
|
|
name="rag_agent",
|
|
role="Você é um assistente útil que pode responder perguntas com a ajuda do WeaviateVectorSearchTool.",
|
|
llm="gpt-4o-mini",
|
|
tools=[weaviate_tool],
|
|
)
|
|
```
|
|
|
|
## Conclusão
|
|
|
|
O `WeaviateVectorSearchTool` fornece uma maneira poderosa de buscar documentos semanticamente similares em um banco de dados vetorial Weaviate. Ao utilizar embeddings vetoriais, ele permite resultados de busca mais precisos e relevantes em termos de contexto, quando comparado a buscas tradicionais baseadas em palavras-chave. Essa ferramenta é especialmente útil para aplicações que precisam encontrar informações a partir do significado e não apenas de correspondências exatas. |