<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Text Search on Qdrant - Vector Search Engine</title><link>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/</link><description>Recent content in Text Search on Qdrant - Vector Search Engine</description><generator>Hugo</generator><language>en-us</language><managingEditor>info@qdrant.tech (Andrey Vasnetsov)</managingEditor><webMaster>info@qdrant.tech (Andrey Vasnetsov)</webMaster><atom:link href="https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/index.xml" rel="self" type="application/rss+xml"/><item><title>Text Filtering</title><link>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/text-filtering/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/text-filtering/</guid><description>&lt;h1 id="text-filtering"&gt;Text Filtering&lt;/h1&gt;
&lt;p&gt;Qdrant supports &lt;a href="https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/filtering/"&gt;filtering&lt;/a&gt; on a wide range of datatypes: numbers, dates, booleans, geolocations, and strings. In Qdrant, a filter is typically combined with a vector query. The vector query is used to score and rank the results, while the filter is used to narrow down the results based on specific criteria.&lt;/p&gt;
&lt;h2 id="text-and-keyword-strings"&gt;Text and Keyword Strings&lt;/h2&gt;
&lt;p&gt;When it comes to filtering on strings, it is important to understand the difference between the two types of strings in Qdrant: text and keyword. These two string types are designed for different use cases: filtering on exact string values or filtering on individual search terms. To filter on exact string values, Qdrant uses &lt;strong&gt;keyword&lt;/strong&gt; strings. Keyword strings are ideal for filtering on strings like IDs, categories, or tags. To filter on individual terms or phrases within a larger body of text, Qdrant uses &lt;strong&gt;text&lt;/strong&gt; strings.&lt;/p&gt;</description></item><item><title>Full-Text Search</title><link>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/full-text-search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/full-text-search/</guid><description>&lt;h1 id="full-text-search"&gt;Full-Text Search&lt;/h1&gt;
&lt;p&gt;Full-text search is similar to full-text filtering, with the key difference being that full-text queries are used for ranking. For each document that matches the search terms, Qdrant calculates a relevance score based on how well the document matches the search terms. That score is used to rank the results. Qdrant supports several full-text search scoring algorithms.&lt;/p&gt;
&lt;p&gt;Full-text search in Qdrant is powered by &lt;a href="https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/articles/sparse-vectors/"&gt;sparse vectors&lt;/a&gt;. Why sparse vectors? Because they are a flexible way to represent data for search purposes, from classic BM25-based search, to semantic search, and &lt;a href="https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/tutorials-search-engineering/collaborative-filtering/"&gt;collaborative filtering&lt;/a&gt;. Each term in the vocabulary corresponds to one or more dimension of the sparse vector, and the values in those dimensions represent the weight of that term in the document. Weights can be calculated using document statistics for use with the &lt;a href="#bm25"&gt;BM25&lt;/a&gt; ranking algorithm, or you can use transformer-based models that can capture semantic meaning, like &lt;a href="#splade"&gt;SPLADE++&lt;/a&gt;, and &lt;a href="#minicoil"&gt;miniCOIL&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Hybrid Search</title><link>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/hybrid-search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/text-search/hybrid-search/</guid><description>&lt;h1 id="combining-semantic-and-lexical-search-using-hybrid-search"&gt;Combining Semantic and Lexical Search using Hybrid Search&lt;/h1&gt;
&lt;p&gt;&lt;a href="https://deploy-preview-2498--condescending-goldwasser-91acf0.netlify.app/documentation/search/hybrid-queries/#hybrid-search"&gt;Hybrid search&lt;/a&gt; enables you to combine semantic and lexical search in a single query, returning results that match the semantic meaning, the exact keywords, or both. This is useful when you don&amp;rsquo;t know whether the user is looking for a specific keyword or a semantically similar document. For example, when searching for books, a user may enter &amp;ldquo;time travel&amp;rdquo; to find books related to the concept of time travel, but they may also enter a book&amp;rsquo;s ISBN to find a specific book. Hybrid queries enable you to return results for both cases in a single query.&lt;/p&gt;</description></item></channel></rss>