<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Search on Dapr Docs</title><link>https://docs.dapr.io/developing-applications/building-blocks/search/</link><description>Recent content in Search on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.dapr.io/developing-applications/building-blocks/search/index.xml" rel="self" type="application/rss+xml"/><item><title>Search overview</title><link>https://docs.dapr.io/developing-applications/building-blocks/search/search-overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.dapr.io/developing-applications/building-blocks/search/search-overview/</guid><description>&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Alpha&lt;/h4>

 The search API is currently in &lt;a href="https://docs.dapr.io/operations/components/certification-lifecycle/#certification-levels">alpha&lt;/a>.

&lt;/div>

&lt;p>Dapr&amp;rsquo;s search API provides a single, portable way to store, retrieve, and query documents in lexical (full-text) search engines such as Meilisearch, Elasticsearch, and OpenSearch. Instead of learning a different SDK and query language for each search engine, your application indexes JSON documents and queries them through the same API, and you swap the underlying engine by changing the &lt;a href="https://docs.dapr.io/reference/components-reference/supported-search/">search component&lt;/a>.&lt;/p>
&lt;p>The search API is scoped to storing and querying documents that are already index-ready. Text extraction, chunking, embedding generation, and ingestion pipeline orchestration are out of scope; your application performs those steps before calling the API. For similarity search over embeddings, use the &lt;a href="https://docs.dapr.io/developing-applications/building-blocks/vector/vector-overview/">vector API&lt;/a> instead.&lt;/p></description></item><item><title>How-To: Index and search documents</title><link>https://docs.dapr.io/developing-applications/building-blocks/search/howto-search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.dapr.io/developing-applications/building-blocks/search/howto-search/</guid><description>&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Alpha&lt;/h4>

 The search API is currently in &lt;a href="https://docs.dapr.io/operations/components/certification-lifecycle/#certification-levels">alpha&lt;/a>.

&lt;/div>

&lt;p>Let&amp;rsquo;s get started using the &lt;a href="https://docs.dapr.io/developing-applications/building-blocks/search/search-overview/">search API&lt;/a>. In this guide, you&amp;rsquo;ll learn how to:&lt;/p>
&lt;ul>
&lt;li>Set up a Meilisearch search component.&lt;/li>
&lt;li>Create an index.&lt;/li>
&lt;li>Index documents and wait for the write to complete.&lt;/li>
&lt;li>Run full-text searches with filters, sorting, and pagination.&lt;/li>
&lt;li>Retrieve and delete documents by ID.&lt;/li>
&lt;/ul>
&lt;p>The HTTP API uses the &lt;a href="https://protobuf.dev/programming-guides/json/">JSON mapping of the protobuf messages&lt;/a>: field names are camelCase, 64-bit integers are strings, and bytes are base64-encoded. Responses include fields set to their zero value and omit optional fields that aren&amp;rsquo;t set. The JavaScript SDK hides these details: document content is a plain object, and enumerations are short strings such as &lt;code>&amp;quot;completed&amp;quot;&lt;/code> or &lt;code>&amp;quot;asc&amp;quot;&lt;/code>.&lt;/p></description></item></channel></rss>