Closed Bug 771716 Opened 13 years ago Closed 12 years ago

remove bucketed search code

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012.14

People

(Reporter: willkg, Assigned: willkg)

Details

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

Cheng said the CTR numbers look like this: > Unified: 162618/248246 65.5% > Bucketed: 163114/250226 65.2% There's virtually no difference there. We've had unified search waffled at 50% for over a week now and given that there's virtually no difference, I propose we ditch the bucketed search code. Why? Because one dimension of search code is much easier to enhance and maintain going forward than two dimensions and if there's virtually no difference between bucketed and unified search results, there's no reason to keep the bucketed search results view around.
If I had my druthers, we'd slide it into the 2012.13 sprint. It should be pretty easy. Probably a 1 pointer. Anyone object?
Go for it!
Agreed! Thanks Will!
Will, I added it to the 2012.13 sprint, under the assumption that this does not affect any of the items in the current sprint. Please change it back, if that assumption is wrong.
Target Milestone: --- → 2012.13
Adding metadata. I think this is a 1pter.
Whiteboard: u=dev c=search p=1
After the flag issue, we need to collect more data before proceeding => moving to next sprint.
Target Milestone: 2012.13 → 2012.14
Grabbing this one and making it a P3 since nothing in this sprint is helped by having this done first. Plus we're waiting on Cheng to see what the CTR numbers look like.
Assignee: nobody → willkg
Priority: P1 → P3
This is still just waiting on Cheng for CTR numbers.
GO FOR IT!
I've got most of this done. There are some minor bits to be cleaned up. I created bug #777721 to cover cleaning up query_fields.
Pretty sure Ricky pushed this to production earlier today.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.