Closed Bug 755923 Opened 14 years ago Closed 13 years ago

RIP: remove sphinx search code

Categories

(support.mozilla.org :: Search, defect, P1)

Product:
support.mozilla.org
Component:
Search
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012.12

People

(Reporter: willkg, Assigned: willkg)

Details

(Whiteboard: u=dev c=search p=2)

Remove Sphinx search code. This involves a bunch of pieces, but this is probably a good list to start with: 1. remove the elasticsearch waffle flag 2. remove the _search_suggestions_sphinx code in apps/questions/views.py and fix _search_suggestions 3. remove the search_with_sphinx code in apps/search/views.py and fix search 4. remove the sphinx-specific stuff from the search results templates 5. remove configs/sphinx 6. remove sphinx from the documentation 7. remove sphinx-specific commands and tests from apps/search and apps/questions
Putting this in 2012.11 which is around mid-June since we want to have this done for 2012 Q2.
Target Milestone: --- → 2012.11
Target Milestone: 2012.11 → 2012.12
Grabbing this one. I'll do some of the work in this bug and spin off another bug with the outstanding bits.
Assignee: nobody → willkg
Q2 goal => P1
Priority: -- → P1
Adding component and all that. Also, making this a 2 pointer. I've done some work on it already. Probably another day of work gets us to a good place. Then we can push the rest off until later.
Whiteboard: u=dev c=search p=2
After all the code changes happen, we still need to nix the sphinx reindexing cronjob. However, I can't figure out what's kicking off the sphinx reindexing cronjob. I don't see it in crontab.tpl. Ricky suggested maybe James knows. James: ?
I have another request for removing the crontab--it's on the Sphinx machines. In pull request: https://github.com/mozilla/kitsune/pull/666
Landed in master in https://github.com/mozilla/kitsune/commit/8405999034bb47f55a2e1a4239f280d1782431b0 Pushed to production just now. Sphinx: Fare well.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.