starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #13812] [CLOSED] Improve search with partial term matching #13721

New Issue
Closed
opened 2026-02-07 07:18:01 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:18:01 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/13812
Author: @TOomaAh
Created: 3/31/2025
Status: ❌ Closed

Base: master ← Head: feature/fuzzy-search

📝 Commits (3)

  • 94ffb23 feat: Improve search functionality with fuzzy matching for partial terms
  • a174944 feat: implement FTS5 search with numeric term support
  • afb4963 refacto: remove unused method

📊 Changes

3 files changed (+125 additions, -2 deletions)

View changed files

📝 Jellyfin.Server.Implementations/Item/BaseItemRepository.cs (+18 -2)
📝 src/Jellyfin.Database/Jellyfin.Database.Implementations/IJellyfinDatabaseProvider.cs (+10 -0)
📝 src/Jellyfin.Database/Jellyfin.Database.Providers.Sqlite/SqliteDatabaseProvider.cs (+97 -0)

📄 Description

Changes
This commit enhances the search functionality by implementing fuzzy matching for partial terms. It modifies how special characters are processed, adds support for shorter tokens in search queries, and improves the handling of numeric parts in search terms. These changes allow users to find content even with incomplete or partially typed search terms, making the search experience more forgiving and user-friendly. This is a test implementation to gather feedback from users and determine the best approach for fuzzy searching in the long term.

I've only been able to test this implementation on a small library with limited content, and the performance appears acceptable with no noticeable delays in search results. However, additional testing on larger libraries would be beneficial to fully understand the performance characteristics of these changes. Users with extensive collections may want to monitor search response times when testing this PR.

image

Issues
Fixes #1674

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/13812 **Author:** [@TOomaAh](https://github.com/TOomaAh) **Created:** 3/31/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `feature/fuzzy-search` --- ### 📝 Commits (3) - [`94ffb23`](https://github.com/jellyfin/jellyfin/commit/94ffb23612d713800141041dc95d8598dcc02011) feat: Improve search functionality with fuzzy matching for partial terms - [`a174944`](https://github.com/jellyfin/jellyfin/commit/a174944042f665a14201b580e24963f38f1f3155) feat: implement FTS5 search with numeric term support - [`afb4963`](https://github.com/jellyfin/jellyfin/commit/afb49634160baa1c5ec6529c8f02a386d6f2b99e) refacto: remove unused method ### 📊 Changes **3 files changed** (+125 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Jellyfin.Server.Implementations/Item/BaseItemRepository.cs` (+18 -2) 📝 `src/Jellyfin.Database/Jellyfin.Database.Implementations/IJellyfinDatabaseProvider.cs` (+10 -0) 📝 `src/Jellyfin.Database/Jellyfin.Database.Providers.Sqlite/SqliteDatabaseProvider.cs` (+97 -0) </details> ### 📄 Description **Changes** This commit enhances the search functionality by implementing fuzzy matching for partial terms. It modifies how special characters are processed, adds support for shorter tokens in search queries, and improves the handling of numeric parts in search terms. These changes allow users to find content even with incomplete or partially typed search terms, making the search experience more forgiving and user-friendly. This is a test implementation to gather feedback from users and determine the best approach for fuzzy searching in the long term. I've only been able to test this implementation on a small library with limited content, and the performance appears acceptable with no noticeable delays in search results. However, additional testing on larger libraries would be beneficial to fully understand the performance characteristics of these changes. Users with extensive collections may want to monitor search response times when testing this PR. ![image](https://github.com/user-attachments/assets/94ccd7bf-ef27-4c7a-84a8-cb9aa18ac016) **Issues** Fixes #1674 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:18:01 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#13721
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?