From 5f48af5b9114d480d7c9bea71c298f1fde001563 Mon Sep 17 00:00:00 2001 From: Marko Henning Date: Wed, 19 Mar 2025 17:04:45 +0100 Subject: [PATCH] Revert the ordering change with chromadb, not necessary with reranker results --- backend/open_webui/retrieval/utils.py | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/backend/open_webui/retrieval/utils.py b/backend/open_webui/retrieval/utils.py index 1afb333b1..d50d4d44c 100644 --- a/backend/open_webui/retrieval/utils.py +++ b/backend/open_webui/retrieval/utils.py @@ -146,12 +146,7 @@ def query_doc_with_hybrid_search( # retrieve only min(k, k_reranker) items, sort and cut by distance if k < k_reranker if k < k_reranker: - if VECTOR_DB == "chroma": - # Chroma uses unconventional cosine similarity, so we don't need to reverse the results - # https://docs.trychroma.com/docs/collections/configure#configuring-chroma-collections - sorted_items = sorted(zip(distances, metadatas, documents), key=lambda x: x[0], reverse=False) - else: - sorted_items = sorted(zip(distances, metadatas, documents), key=lambda x: x[0], reverse=True) + sorted_items = sorted(zip(distances, metadatas, documents), key=lambda x: x[0], reverse=True) sorted_items = sorted_items[:k] distances, documents, metadatas = map(list, zip(*sorted_items)) result = {