immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

[PR #2331] [MERGED] fix(server): use current schema for search/explore #9496

New Issue
Closed
opened 2026-02-05 14:05:47 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 14:05:47 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/immich-app/immich/pull/2331
Author: @jrasm91
Created: 4/25/2023
Status: ✅ Merged
Merged: 4/25/2023
Merged by: @alextran1502

Base: main ← Head: fix/use-most-recent-schema

📝 Commits (1)

  • c9b003b fix(server): use current schema for search/explore

📊 Changes

1 file changed (+4 additions, -11 deletions)

View changed files

📝 server/libs/infra/src/repositories/typesense.repository.ts (+4 -11)

📄 Description

Previously, typesense would only uses fully-indexed collections. This changes that to always use the most recent collection, regardless of index status. The results of this change should be:

  1. Explore/search functionality is available sooner on new installs (searchable as they're being indexed)
  2. Migrations won't break search/explore with 400 Bad Request errors while indexing is happening (if explore references a new field, that doesn't exist in the old schema, it would lead to this situation)

Related to:

🔄 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/immich-app/immich/pull/2331 **Author:** [@jrasm91](https://github.com/jrasm91) **Created:** 4/25/2023 **Status:** ✅ Merged **Merged:** 4/25/2023 **Merged by:** [@alextran1502](https://github.com/alextran1502) **Base:** `main` ← **Head:** `fix/use-most-recent-schema` --- ### 📝 Commits (1) - [`c9b003b`](https://github.com/immich-app/immich/commit/c9b003beccb8b6667c53d142e4fdaadcad5700ab) fix(server): use current schema for search/explore ### 📊 Changes **1 file changed** (+4 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `server/libs/infra/src/repositories/typesense.repository.ts` (+4 -11) </details> ### 📄 Description Previously, typesense would only uses fully-indexed collections. This changes that to always use the most recent collection, regardless of index status. The results of this change should be: 1. Explore/search functionality is available sooner on new installs (searchable as they're being indexed) 2. Migrations won't break search/explore with 400 Bad Request errors while indexing is happening (if explore references a new field, that doesn't exist in the old schema, it would lead to this situation) Related to: - #2330 --- <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-05 14:05:47 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
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: immich-app/immich#9496
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?