검색에서 태그 동의어가 작동하지 않아요

Eviepayne · 4월 21, 2025, 1:08오전

포럼에서 tags:tag1로 검색할 때, tag1이 tag-one의 동의어라면 결과가 표시되지 않고 tag-one이 포함된 게시글도 검색되지 않습니다.

Eviepayne · 4월 22, 2025, 1:16오후

이것은 의도된 동작이 아닐 것 같아 버그로 표시하겠습니다.

sam · 4월 23, 2025, 5:30오전

알겠습니다. 여기에서 동의어 처리를 추가해야 할 것 같네요. 동의합니다.

커뮤니티가 도움을 주길 원할 경우를 대비해 이 이슈에 pr-welcome 태그를 달아두겠습니다. 검색 기능은 매우 독립적으로 구현되어 있어, 테스트를 작성하는 것도 아주 간단할 것입니다.

Moin · 2월 12, 2026, 9:32오전

수정 완료

이제 다음 검색이 모두 정상적으로 작동합니다:
Search for tag:howto
Search for tag:how-to
Search for #howto
Search for #how-to

github.com/discourse/discourse

FIX: Resolve tag synonyms in search and filter queries (#37628)

main ← fix/tag-synonyms-in-search

merged 07:57AM - 09 Feb 26 UTC

tgxworld

+109 -24

What is the problem? Discourse allows admins to mark a tag as a synonym of anot…her tag. For example, "brunch" can be made a synonym of "lunch". When this happens, all topics tagged with "brunch" are automatically retagged with "lunch", and the `tags.target_tag_id` column on the synonym tag record is set to point to the target tag. However, several code paths did not account for synonyms: 1. **Search:** `Search#search_tags` and the hashtag advanced filter did not resolve synonyms. When a user searched using a synonym name (e.g. `tags:brunch`, `tags:brunch+eggs`, or `#brunch`), no results were returned because: - The `tags:` comma path queries `topic_tags` joined with `tags` by name, but topics are tagged with the target tag "lunch", not the synonym "brunch". - The `tags:` plus path aggregates tag names per topic into a tsvector and matches against the searched name, but the aggregated names are target tag names, so "brunch" never matches. - The `#` hashtag path picks the synonym tag's own `id` and queries `topic_tags` by that ID, but topics store the target tag's ID. 2. **Filter route:** `TopicsFilter#tag_ids_from_tag_names` concatenated both the synonym's own ID and the target tag ID. For match-all queries (e.g. `tag:brunch`), this required a topic to have both IDs in `topic_tags`, which never happens since only the target tag ID is stored. For negation queries (e.g. `-tag:brunch`), the exclusion targeted the synonym ID rather than the target, so no topics were excluded. What is the solution? In `Search#search_tags`, add a synonym resolution step before the existing comma/plus branching logic. It splits the match string into individual tag names, queries for any that are synonyms via `Tag.where_name(tag_names).where.not(target_tag_id: nil)`, builds a name mapping, and replaces synonym names with their target tag names. The replacement operates on the split array elements rather than using substring replacement to avoid corrupting tag names that may contain other tag names as substrings. In the hashtag advanced filter, pick both `:id` and `:target_tag_id` from the tag lookup and prefer `target_tag_id` when present, so the query uses the target tag's ID instead of the synonym's own ID. In `TopicsFilter#tag_ids_from_tag_names`, replace the transpose/concat approach with `.map { |id, target_id| target_id || id }` to resolve each tag to its canonical ID — the target for synonyms, or the tag's own ID otherwise. A partial index on `tags.target_tag_id` is added (scoped to `WHERE target_tag_id IS NOT NULL`) to support efficient synonym lookups.

nat · 2월 14, 2026, 12:00오전

이 주제는 38시간 후 자동으로 닫혔습니다. 더 이상 새 답글을 작성할 수 없습니다.

글		댓글	조회수
Tags confusing (to all or me only) Product Support tags	4	312	6월 9, 2024
Show original tag even if synonym tag is added Product Support	0	66	8월 2, 2024
Don't show tag synonyms in suggestion lists Feature	6	841	7월 20, 2023
Merging tags - Tag Synonyms Feature completed , tags	22	5848	1월 22, 2020
Add search synonyms Feature	17	6352	6월 1, 2023

검색에서 태그 동의어가 작동하지 않아요

Related topics