'vector database' 검색 결과

Store and query vector embeddings using Amazon S3 Vectors, a cost-effective long-term vector storage service with its own API namespace (s3vectors). Triggers on: create S3 vector bucket, vector index, store embeddings, semantic search, RAG vector storage, similarity search, vector database, migrate from other vector databases. Do NOT use for: querying tabular data (use querying-data-lake), S3 object storage, or hundreds/thousands of sustained QPS (use OpenSearch).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Serverless vector database at the edge with Cloudflare Vectorize. Use when: building semantic search on Cloudflare Workers, RAG pipelines at the edge, low-latency vector similarity search, or storing and querying embeddings without managing a separate vector database.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with the @upstash/vector TypeScript/JavaScript SDK, a serverless vector database for embeddings, similarity search, semantic search, and RAG (retrieval-augmented generation). Use when upserting, querying, fetching, ranging, or deleting vectors, upserting raw text against an index with a built-in embedding model, choosing dense, sparse, or hybrid indexes, filtering by metadata, organizing data with namespaces, running resumable queries, or connecting Upstash Vector to an AI or LLM application. Also use when the user asks for a vector store, vector search, nearest-neighbor or kNN search, embeddings storage, semantic cache, recommendations or similarity features, or a hosted vector index that needs no infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess the security of RAG systems, which retrieve documents to support AI answers. Test whether stored vectors expose source text, leak documents between tenants, or allow inserted content to dominate search results, then document findings and controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing source-text exposure from stored vectors
• Checking data isolation between tenants
• Testing retrieval manipulation in a test collection

Build and operate LLM applications with guidance on RAG, which uses retrieved documents to inform answers. Covers document indexing, vector database selection, prompt improvement, response evaluation, caching, and estimates of model usage costs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building an assistant that answers from documents
• Choosing a vector database for document search
• Comparing answer quality after prompt changes

Hunt vector-store / embedding-layer weaknesses in RAG pipelines (OWASP LLM08 Vector and Embedding Weaknesses) — persistent corpus poisoning that survives across sessions and users (distinct from one-shot indirect prompt injection, which is owned by hunt-llm-ai), cross-tenant vector-database IDOR (unauthenticated or unscoped queries against Pinecone/Weaviate/Chroma/Milvus/Qdrant/pgvector), source-text/metadata leakage in similarity-search results, and retrieval-hijack via adversarial embedding proximity ('SEO poisoning' for RAG). Targets: any app with a shared knowledge base, document upload feeding a chatbot, or a directly reachable vector-DB port. Validate: a second, clean session/account must inherit a poisoned result, or a cross-tenant artifact must be independently verifiable — confabulation is not a finding, same bar as hunt-llm-ai. Use when target is RAG-backed, exposes a vector-DB port, or lets users upload documents that other users' queries later retrieve.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

RAG Builder with Parallel Document Processing Vector database construction with local embeddings (zero cost) Handles PDF download, text extraction, chunking, and vector database creation Absorbed B5 (Parallel Document Processor) capabilities Use when: building RAG, creating vector database, downloading PDFs, embedding documents, batch processing Triggers: build RAG, create vector database, download PDFs, embed documents, batch PDF processing

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Database specialist for SQL, NoSQL, and vector database modeling, schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning, data standards, anti-pattern review, and compliance-aware database design. Use for database, schema, ERD, table design, document model, vector index design, RAG retrieval architecture, migration, query tuning, glossary, capacity estimation, backup strategy, database anti-pattern remediation work, and ISO 27001, ISO 27002, or ISO 22301-aware database recommendations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Database for PostgreSQL development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Flexible Server, pgvector/Apache AGE, Private Link/TLS, replicas/PITR, or Azure AI/ML integrations, and other Azure Database for PostgreSQL related development tasks. Not for Azure SQL Database (use azure-sql-database), Azure SQL Managed Instance (use azure-sql-managed-instance), SQL Server on Azure Virtual Machines (use azure-sql-virtual-machines), Azure Database for MySQL (use azure-database-mysql).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design an enterprise search system that answers questions using retrieved company content, an approach called RAG. Gather requirements and produce architecture diagrams, deployment guidance, and validation plans using GKE, AlloyDB, and open models.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing conversational search for internal documents
• Planning RAG with a vector-enabled SQL database
• Hosting open models on GKE

Design hybrid search on AlloyDB by combining meaning-based search, keywords, and SQL filters. Turn requirements into architecture diagrams, database setup scripts, deployment guidance, and validation plans for search applications on Google Cloud.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing product search with meaning-based matching and attribute filters
• Planning result reranking and AI quality checks
• Preparing AlloyDB and Cloud Run deployment guidance

Design and implement RAG systems, which retrieve documents to inform AI answers. Get document preparation strategies, vector database comparisons, combined keyword and meaning-based search, result reranking, and an evaluation plan for retrieval quality.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design an AI application that answers using internal documents
• Compare vector databases and document splitting strategies
• Improve search through keyword matching and result reranking

Provides configuration patterns for LangChain4J vector stores in RAG applications. Use when building semantic search, integrating vector databases (PostgreSQL/pgvector, Pinecone, MongoDB, Milvus, Neo4j), implementing embedding storage/retrieval, setting up hybrid search, or optimizing vector database performance for production AI applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build systems that use Pinecone to find documents for AI answers or retain agent memories across sessions. Guides index setup, data loading, meaning-based and keyword search, memory separation, and end-to-end checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build an AI assistant that answers from documents
• Keep agent facts and decisions across sessions
• Combine meaning-based search with exact terminology

Build document search and AI retrieval workflows with Chroma, a database for numerical representations of text. Cover document storage, meaning-based search, metadata filters, persistence, and connections to LangChain and LlamaIndex.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building document search based on meaning
• Adding document retrieval to AI answers
• Filtering search results by document attributes

Design a RAG pipeline that retrieves documents to support AI answers. Analyze document splitting, select embedding models and vector databases, and evaluate retrieval quality using test queries and known relevant documents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a RAG system for internal documents
• Choosing how to split documents for search
• Comparing embedding models and vector databases

Build document search and AI retrieval workflows with Chroma, a database for numerical representations of text. Cover document storage, meaning-based search, metadata filters, persistence, and connections to LangChain and LlamaIndex.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building document search based on meaning
• Adding document retrieval to AI answers
• Filtering search results by document attributes

Assess web applications and APIs for SQL injection, where input changes database queries. The skill covers finding vulnerable inputs, testing different database systems, automating checks, and documenting findings with remediation suggestions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing web application inputs for SQL injection
• Reviewing GraphQL and WebSocket injection risks
• Combining SQLmap automation with manual verification

Assists with storing, searching, and managing vector embeddings using ChromaDB. Use when building RAG pipelines, semantic search engines, or recommendation systems. Trigger words: chromadb, chroma, vector database, embeddings, semantic search, similarity search, vector store, rag.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for high-performance Vector Databases, Deep RAG architectures, pgvector 0.8+ HNSW, Reciprocal Rank Fusion (RRF), Cross-Encoder Re-ranking, and Late Chunking / Panduan ahli Vector DB, arsitektur Deep RAG, pgvector HNSW, RRF, dan Re-ranking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Discovers requirements and generates architectural, design, and deployment guidance for dynamic hybrid search systems by combining semantic search and keyword search. Optimized for AlloyDB hybrid search use cases in Google Cloud. Use when users need vector search combined with structured SQL filtering, faceted attributes, semantic reranking, in-database AI validation, or serverless hosting across transactional relational databases, analytical data warehouses, or managed database engines. DON'T use this skill for simple keyword-only search, or when a standalone non-relational vector database is required.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similarity search. Use PROACTIVELY for vector search implementation, embedding optimization, or semantic retrieval systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sets up vector databases for semantic search including Pinecone, Chroma, pgvector, and Qdrant with embedding generation and similarity search. Use when users request "vector database", "semantic search", "embeddings storage", "Pinecone setup", or "similarity search".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build advanced AgentDB workflows with database synchronization, multiple databases, and search that combines meaning with attribute filters. Covers similarity measures, diverse search results, and operational patterns for distributed AI applications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sharing stored patterns across multiple AgentDB instances
• Filtering semantic search by date or category
• Separating knowledge and conversation databases