gorse-io / gorse-io/gorse

No such index documents error after migration to 0.5.11

Open
#1,359 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
9.8k
Forks
912
Avg merge
2h 35m
Merged PRs (30d)
9

Description

Please answer these questions before submitting your issue. Thanks!

**Gorse version**
(gorse-in-one:0.5.11)

**Describe the bug**
After migrating from 0.5.10 to 0.5.11, the recommend apis like '/api/feedback/non-personalized/popular, /api/feedback/:userId' returns this response: "No such index documents" error.

**To Reproduce**
Migrate from 0.5.10 to 0.5.11 and call recommends api. No change in postgres db.

**Expected behavior**
Api must return response without error

**Additional context**
Remigrating to 0.5.10 solves problem.

Thanks in advance

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the 0.5.10-to-0.5.11 migration without changing PostgreSQL, then call /api/feedback/non-personalized/popular and /api/feedback/:userId. Trace where the "No such index documents" response is produced; done means both recommend APIs return successfully after migration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, postgresql
Domain
api, backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.