From 01d5c473a86e2d16e7fc5f4a437b7a8c1c0403b5 Mon Sep 17 00:00:00 2001 From: Atita Arora Date: Thu, 29 Feb 2024 10:35:37 +0100 Subject: [PATCH] Update qdrant-landing/content/blog/case-study-dailymotion.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Kacper Łukawski --- qdrant-landing/content/blog/case-study-dailymotion.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/qdrant-landing/content/blog/case-study-dailymotion.md b/qdrant-landing/content/blog/case-study-dailymotion.md index fd3bd78c1..8802ddaed 100644 --- a/qdrant-landing/content/blog/case-study-dailymotion.md +++ b/qdrant-landing/content/blog/case-study-dailymotion.md @@ -117,7 +117,8 @@ Looking at the complexity, scale and adaptability of the desired solution, the t Qdrant API’s have been immensely easy to get started with as compared to Google Vertex Matching Engine (which was Dailymotion’s initial choice) and the support from the team has been of a huge value to us. -**8. Being able to fetch data by id:** +**8. Being able to fetch data by id** + Qdrant allows to retrieve vector point / videos by ids while the Vertex Matching Engine requires a vector input to be able to search for other vectors which was another really important feature for Dailymotion