Results for “embedding-search”

Provides Qdrant vector database integration patterns with LangChain4j. Handles embedding storage, similarity search, and vector management for Java applications. Use when implementing vector-based retrieval for RAG systems, semantic search, or recommendation engines.

Local RAG indexing with 97% storage reduction via anchor-based lazy recomputation. Graph-based selective embedding storage for memory-efficient semantic code search.

Use when the user asks to design RAG pipelines, optimize retrieval strategies, choose embedding models, implement vector search, or build knowledge retrieval systems.

Reference for configuring and using LangChain4j vector stores, covering setup, search, filtering, and ingestion.

Build production-ready LLM applications, RAG systems, and intelligent agents with architecture design, model selection, and cost controls.

Enables zero-shot image classification, image-text matching, and cross-modal retrieval using OpenAI's CLIP model, with code for semantic search, content moderation, and vector database integration.

Provides persistent, compounding memory for AI agents across sessions using local markdown files, with optional Supabase-backed semantic search.

Provides persistent, self-hosted semantic memory for AI agents via MCP, storing worklogs, decisions, and notes in PostgreSQL with pgvector for meaning-based retrieval across sessions.

Provides best practices for using MariaDB's built-in vector support for AI workloads, including SQL syntax for vector columns, indexes, distance functions, and RAG patterns.

Comprehensive toolkit for developing with the CocoIndex library. Use when users need to create data transformation pipelines (flows), write custom functions, or operate flows via CLI or API. Covers building ETL workflows for AI data processing, including embedding documents into vector databases, building knowledge graphs, creating search indexes, or processing data streams with incremental updates.

Use when running analytical SQL over Parquet/CSV/JSON without a warehouse, replacing pandas for data wrangling, joining S3 data in-place, building local data marts, or embedding OLAP into an app. Triggers: read_parquet/read_csv setup, partitioned dataset queries, hive partitioning, glob patterns for S3, COPY TO export, attach Postgres/MySQL, UDFs in Python/R, MotherDuck cloud sync, columnar performance vs row stores. NOT for OLTP workloads (concurrent writes), distributed analytics at petabyte scale (use Spark/Trino), or vector search (use pgvector/Lance).