Esta página foi traduzida automaticamente. Leia o original em inglês.

Component

core/datastore/qdrant

A Qdrant vector database. Stores embedding vectors alongside their payloads and answers nearest-neighbour queries over them, so an application that retrieves reference material by similarity is wired to this component rather than to a general-purpose store. Collections are created through Qdrant's own API at runtime; the component declares the server, not its contents. It is realized on Kubernetes and, for local development, on Docker Compose, and exports its host, its HTTP port and its gRPC port to consumers via the uses topology. On Kubernetes there are two realizations and the Manifest chooses between them. `qdrant` synthesizes the server as a workload and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `qdrant-chart` renders the product's own Helm chart, which additionally carries its maintainers' start-up script, data-volume ownership step and pre-stop pause, so reach for it where a chart repository is reachable at build time. That chart also renders an interaction check — a Pod annotated as a test hook, whose script deletes and recreates a collection named `test_collection` on the running server — which the chart offers no setting to decline; the chart realization's own description states what it does and when it runs. While api_key is filled, a scrape of `metrics_endpoint` presents on its connection's `credential` the key attached to read_only_api_key, or the api_key where that slot is empty. The read-only key still reads every collection: it makes a scraper read-only, not metrics-only. `aggrega lint --release` reports such a credential as differing from api_key, as expected.

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:b0961eaec3c3ddc6f6ae0d3771b7faaa9af174699cd4091865afdbcc336888f3
Publicado
2026-11-10T10:11:02Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:3956ba12160a8653d222816071fc47fb42e4a1f7aefcef46cba0d66eb1ad3db5

Referência nesta versão

oci://hub.aggrega.ai/component/core/datastore/qdrant:1.0.0

Parâmetros do desenvolvedor

Valores que o desenvolvedor define no Aggregate.

NomeTipoPadrãoObrigatórioDescrição
log_levelstring—nãoServer log verbosity (TRACE, DEBUG, INFO, WARN or ERROR). Omit to use the server default (INFO).
max_request_size_mbinteger (min 1)—nãoLargest request body the server accepts, in mebibytes. Omit to use the server default (32).
telemetry_disabledbooleanfalsenãoStop the server reporting anonymous usage telemetry to its maintainers. Off by default, matching the server's own default.

Dimensionamento do operador

Dimensionamento de infraestrutura que o operador ajusta por ambiente.

NomeTipoPadrãoObrigatórioDescrição
portinteger (min 1024, max 65535)6333nãoHTTP (REST) listen port. Most operators should omit this and let the Recipe assign the default (6333).
grpc_portinteger (min 1024, max 65535)6334nãogRPC listen port, published alongside the HTTP port for clients that prefer it. Most operators should omit this and let the Recipe assign the default (6334).
engine_versionstringv1.19.0nãoQdrant container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag.
source_versionstring—nãoVersion of the Helm chart the chart-backed realization pulls. Read only by that realization; the workload-synthesis and Compose realizations pull no source artifact and ignore it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart.
computeobject—não—
storageobject—não—
overridesobject (open)—nãoProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de saída

Valores que este componente publica para os consumidores pela topologia uses.

NomeTipoPadrãoObrigatórioDescrição
hoststring—simIn-cluster DNS name of the Service fronting the vector database. A consumer dials this name together with whichever of the two published ports its client speaks.
portinteger—simTCP port the REST API is served on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
grpc_portinteger—nãoTCP port the gRPC API is served on, published beside the REST port for a client that prefers it. It is a second listener on the same server, not an alternative address.
protocolstring—nãoHow the published address is spoken to on `port` — `http`, so a consumer reaching the REST API composes its address on that scheme.
metrics_endpointstring—nãoThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics`, on the REST port. While the api_key slot is filled the server answers it only to a key it holds, so a scrape presents one on its connection's `credential` slot: the read-only key where read_only_api_key is filled, and the api_key otherwise.

Sockets uses

Os sockets de dependência pelos quais este componente se conecta. O destino de cada conexão ligada por um socket deve satisfazer o seletor de rótulos dele, e cada conexão pode carregar um acoplamento nos slots que o socket declara. Cada conexão que o Aggregate ou a Release liga pelo socket deve preencher os slots obrigatórios.

Nenhum socket uses declarado.

Slots de acoplamento

Pontos de vinculação nomeados nos quais uma Feature se acopla a este componente. O seletor de um slot restringe qual Feature pode preenchê-lo, e sua lista inject indica como o material da Feature pode ser entregue. Um slot obrigatório deve estar vinculado em cada instância, por um acoplamento na instância ou em um escopo acima dela, e um slot sensível é declarado para lidar com material secreto. Uma Feature também pode se acoplar com um nome que nenhum slot declara.

SlotSeletorObrigatórioInjeçãoSensívelDescrição
api_keyfeature.aggrega.ai/kind=secretnãoenvsimOptional service API-key credential. When attached, every request to the server must present this key, or for a read the key attached to read_only_api_key; unattached, the server accepts unauthenticated requests.
read_only_api_keyfeature.aggrega.ai/kind=secretnãoenvsimOptional read-only API key, filled beside api_key. When attached, the server also accepts this key and answers it with read access to every collection and to its metrics, refusing any write made with it; a scrape of metrics_endpoint presents it in place of api_key, and `aggrega lint --release` then reports that scrape's credential as differing from api_key, which is expected, since the server holds both keys. Filled without api_key, the build halts.

Lista de permissões de autoinjeção

env

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

Esta entidade não usa nada do catálogo.

Usado por

Referência do conceito Component →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade