Closed
Bug 885309
Opened 12 years ago
Closed 12 years ago
Duplicate questions in the search index
Categories
(support.mozilla.org :: Search, defect, P1)
support.mozilla.org
Search
Tracking
(Not tracked)
RESOLVED
FIXED
2013Q3
People
(Reporter: rrosario, Assigned: willkg)
Details
(Whiteboard: u=user c=search p=2 s=2013.13)
Something is causing questions to appear in the index multiple times.
See:
https://support.mozilla.org/en-US/forums/contributors/709276
An example is:
https://support.mozilla.org/search?q=&asked_by=dick888&answered_by=&w=2&a=1&sortby=1
Although, that might go away as soon as we reindex.
| Assignee | ||
Comment 2•12 years ago
|
||
I wonder if we're indexing a question by different document ids in different places. Maybe the update_questions_vote_task (or whatever it's called) is using a different document id than we're using in the indexing methods in QuestionMappingType (or whatever it's called)?
| Reporter | ||
Comment 3•12 years ago
|
||
Putting into the next sprint as I haven't had a chance to dig too deep here. Unassigning myself in case somebody else can get to it first.
Making it a 2pt as a initial guess. I looked a little and it didn't look like a quick thing to troubleshoot.
Assignee: rrosario → nobody
Whiteboard: u=user c=search p= s=2013.12 → u=user c=search p=2 s=2013.13
| Assignee | ||
Comment 5•12 years ago
|
||
| Assignee | ||
Comment 6•12 years ago
|
||
Fix landed in master in https://github.com/mozilla/kitsune/commit/fecf18a
This will prevent new duplicate questions, but we need to wipe the index of the old ones. I'll do that later today.
| Assignee | ||
Comment 7•12 years ago
|
||
Pushed out a two-step reindexing and the problem questions are now gone.
I did a grep across the codebase for other instances of document_id and didn't see any.
I no longer see duplicate questions in the urls provided in the description.
I'm pretty sure fecf18a should fix this issue.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: 2013Q2 → 2013Q3
You need to log in
before you can comment on or make changes to this bug.
Description
•