<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Module 1: Multi-Vector Representations for Textual Data on Qdrant - Vector Search Engine</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/</link><description>Recent content in Module 1: Multi-Vector Representations for Textual Data 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-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/index.xml" rel="self" type="application/rss+xml"/><item><title>Late Interaction Basics</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/late-interaction-basics/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/late-interaction-basics/</guid><description>&lt;div class="date">
 &lt;img class="date-icon" src="https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/icons/outline/date-blue.svg" alt="Calendar" /> Module 1 
&lt;/div>

&lt;h1 id="late-interaction-basics">Late Interaction Basics&lt;/h1>
&lt;p>When building a search system, one fundamental question emerges: &lt;strong>when should a query and document interact?&lt;/strong> The answer to this question may affect both the quality of search results and the system&amp;rsquo;s scalability.&lt;/p>
&lt;p>This lesson introduces the late interaction paradigm - the foundation of multi-vector search - and explores how it compares to other approaches.&lt;/p>
&lt;hr>
&lt;div class="video">
&lt;iframe
 src="https://www.youtube-nocookie.com/embed/8HrvD5o2w8M?rel=0"
 frameborder="0"
 allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
 referrerpolicy="strict-origin-when-cross-origin"
 allowfullscreen>
&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;p>&lt;strong>Follow along in Colab:&lt;/strong> &lt;a href="https://colab.research.google.com/github/qdrant/examples/blob/master/course-multi-vector-search/module-1/late-interaction-basics.ipynb">
&lt;img src="https://colab.research.google.com/assets/colab-badge.svg" style="display:inline; margin:0;" alt="Open In Colab"/>
&lt;/a>&lt;/p></description></item><item><title>MaxSim Distance Metric</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/maxsim-distance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/maxsim-distance/</guid><description>&lt;div class="date">
 &lt;img class="date-icon" src="https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/icons/outline/date-blue.svg" alt="Calendar" /> Module 1 
&lt;/div>

&lt;h1 id="maxsim-distance-metric">MaxSim Distance Metric&lt;/h1>
&lt;p>MaxSim (Maximum Similarity) is the core distance metric for late interaction models. Unlike traditional vector similarity metrics that operate on pairs of single vectors, MaxSim computes similarity between sequences of vectors.&lt;/p>
&lt;p>Understanding MaxSim is important for working with multi-vector search effectively and understanding its performance characteristics.&lt;/p>
&lt;hr>
&lt;div class="video">
&lt;iframe
 src="https://www.youtube-nocookie.com/embed/JvSvuK19m8A?rel=0"
 frameborder="0"
 allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
 referrerpolicy="strict-origin-when-cross-origin"
 allowfullscreen>
&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;p>&lt;strong>Follow along in Colab:&lt;/strong> &lt;a href="https://colab.research.google.com/github/qdrant/examples/blob/master/course-multi-vector-search/module-1/maxsim-distance.ipynb">
&lt;img src="https://colab.research.google.com/assets/colab-badge.svg" style="display:inline; margin:0;" alt="Open In Colab"/>
&lt;/a>&lt;/p>
&lt;hr>
&lt;h2 id="the-maxsim-formula">The MaxSim Formula&lt;/h2>
&lt;p>In late interaction, we represent documents and queries as sequences of token vectors. But how do we measure similarity between two sets of vectors?&lt;/p></description></item><item><title>Use Cases for Multi-Vector Search</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/use-cases-multi-vector/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/use-cases-multi-vector/</guid><description>&lt;div class="date">
 &lt;img class="date-icon" src="https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/icons/outline/date-blue.svg" alt="Calendar" /> Module 1 
&lt;/div>

&lt;h1 id="use-cases-for-multi-vector-search">Use Cases for Multi-Vector Search&lt;/h1>
&lt;p>&lt;strong>When is the added complexity of multi-vector search actually worth it?&lt;/strong> Multi-vector representations require more storage, more computation, and more careful implementation than simple single-vector embeddings. So why bother?&lt;/p>
&lt;p>The answer comes down to one core capability: &lt;strong>fine-grained matching&lt;/strong>. In the previous lessons, you learned how late interaction preserves token-level representations and how MaxSim computes similarity through independent token matching. Now you&amp;rsquo;ll see when this precision actually matters - and when it doesn&amp;rsquo;t.&lt;/p></description></item><item><title>Problems of Multi-Vector Search</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/problems-multi-vector/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/problems-multi-vector/</guid><description>&lt;div class="date">
 &lt;img class="date-icon" src="https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/icons/outline/date-blue.svg" alt="Calendar" /> Module 1 
&lt;/div>

&lt;h1 id="problems-of-multi-vector-search">Problems of Multi-Vector Search&lt;/h1>
&lt;p>Multi-vector search delivers impressive retrieval quality, but it comes with significant challenges. Before deploying multi-vector search in production, you need to understand these limitations and plan accordingly.&lt;/p>
&lt;p>The good news: Module 3 covers optimization techniques that address many of these challenges.&lt;/p>
&lt;hr>
&lt;div class="video">
&lt;iframe
 src="https://www.youtube-nocookie.com/embed/vQKF1hO7hzU?rel=0"
 frameborder="0"
 allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
 referrerpolicy="strict-origin-when-cross-origin"
 allowfullscreen>
&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;h2 id="the-indexing-challenge-why-hnsw-doesnt-work">The Indexing Challenge: Why HNSW Doesn&amp;rsquo;t Work&lt;/h2>
&lt;p>One of the fundamental challenges with multi-vector search stems from &lt;strong>HNSW indexing incompatibility&lt;/strong>. As you learned in the MaxSim lesson, traditional vector search relies on HNSW (Hierarchical Navigable Small World) graphs to enable fast approximate nearest neighbor search. HNSW works by building static proximity graphs that connect similar documents, allowing efficient traversal during queries.&lt;/p></description></item><item><title>Multi-Vector Embeddings in Qdrant</title><link>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/multi-vector-in-qdrant/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/course/multi-vector-search/module-1/multi-vector-in-qdrant/</guid><description>&lt;div class="date">
 &lt;img class="date-icon" src="https://deploy-preview-2256--condescending-goldwasser-91acf0.netlify.app/icons/outline/date-blue.svg" alt="Calendar" /> Module 1 
&lt;/div>

&lt;h1 id="multi-vector-embeddings-in-qdrant">Multi-Vector Embeddings in Qdrant&lt;/h1>
&lt;p>You&amp;rsquo;ve learned how MaxSim enables fine-grained token-level matching and explored both the benefits and challenges of multi-vector search. Now it&amp;rsquo;s time to put that knowledge into practice.&lt;/p>
&lt;p>Qdrant provides first-class support for multi-vector embeddings, making it straightforward to build search systems that leverage late interaction. In this lesson, you&amp;rsquo;ll learn how to configure Qdrant collections for multi-vector search, index documents with token-level embeddings, and execute queries using MaxSim distance.&lt;/p></description></item></channel></rss>