Closed
Bug 729319
Opened 12 years ago
Closed 12 years ago
Hide threads that have no answers from /questions list after 90 days
Categories
(support.mozilla.org :: Forum, task, P1)
support.mozilla.org
Forum
Tracking
(Not tracked)
RESOLVED
FIXED
2012.6
People
(Reporter: igarcia, Assigned: rrosario)
References
Details
(Whiteboard: u=user c=questions p=2)
Threads with no answers should be removed from the view and search indexes 3 months after their creation. After one month, we should add a "noindex" meta tag to make sure that is removed from Google on time. The threads should be left in the DB for reference.
Updated•12 years ago
|
Whiteboard: u=contributor c=questions s=2012.5 p=
Updated•12 years ago
|
Priority: -- → P1
Comment 1•12 years ago
|
||
This is going to make the current "worst query on the site" (which counts the number of questions to show) exponentially worse. (Caching this query for 15 minutes dropped DB load by approximately 80%.) If we're going to do this, I'd propose a small UI change to questions pagination that would let us drop this query, and it should be a blocker for this bug. We should drop the full paginator and just go with Previous, Next links. c.f. Reddit. That means we'd never have to count how many visible questions there are, which means we could drop that query completely. The downside is that users couldn't jump to page X via the UI, and they wouldn't know they were on the last page until we said something like "there's nothing here". But there are so many pages right now that I doubt anyone ever goes that far, anyway.
Comment 2•12 years ago
|
||
(In reply to James Socol [:jsocol, :james] from comment #1) > This is going to make the current "worst query on the site" (which counts > the number of questions to show) exponentially worse. (Caching this query > for 15 minutes dropped DB load by approximately 80%.) > > If we're going to do this, I'd propose a small UI change to questions > pagination that would let us drop this query, and it should be a blocker for > this bug. If I understand what we're talking about here, this query will go away when we split the ES and Sphinx code because because we'll be able to get search results and everything we need to show them entirely from ES without touching the DB. I'm hoping to work on bug #728422 in the 2012.5 sprint (i.e. the next one) which will fix this on the ES side. Does that help?
Comment 3•12 years ago
|
||
(In reply to Will Kahn-Greene [:willkg] from comment #2) > (In reply to James Socol [:jsocol, :james] from comment #1) > > This is going to make the current "worst query on the site" (which counts > > the number of questions to show) exponentially worse. (Caching this query > > for 15 minutes dropped DB load by approximately 80%.) > > > > If we're going to do this, I'd propose a small UI change to questions > > pagination that would let us drop this query, and it should be a blocker for > > this bug. > > If I understand what we're talking about here, this query will go away when > we split the ES and Sphinx code because because we'll be able to get search > results and everything we need to show them entirely from ES without > touching the DB. > > I'm hoping to work on bug #728422 in the 2012.5 sprint (i.e. the next one) > which will fix this on the ES side. > > Does that help? Nevermind--my head is in the search gutter.
Comment 4•12 years ago
|
||
(In reply to Will Kahn-Greene [:willkg] from comment #3) > (In reply to Will Kahn-Greene [:willkg] from comment #2) > > If I understand what we're talking about here, this query will go away when > > we split the ES and Sphinx code because because we'll be able to get search > > results and everything we need to show them entirely from ES without > > touching the DB. > Nevermind--my head is in the search gutter. That may be true, but you raise a good point: there are at least 2 bugs here. One to exclude these from search results, another to exclude them from the /questions view.
Should I create another bug and rename this to refer to only one of the parts?
Assignee | ||
Updated•12 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Summary: Hide threads that have no answers → Hide threads that have no answers from /questions list
Assignee | ||
Comment 6•12 years ago
|
||
Filed Bug 731183 and and Bug 731185.
Assignee | ||
Comment 7•12 years ago
|
||
Filed Bug 731194 for the UI proposal from Comment 1. Either way we have to be careful here not to make performance worse than it already is.
Whiteboard: u=contributor c=questions s=2012.5 p= → u=contributor c=questions s=2012.5 p=2
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Updated•12 years ago
|
Summary: Hide threads that have no answers from /questions list → Hide threads that have no answers from /questions list after 90 days
Assignee | ||
Updated•12 years ago
|
Target Milestone: --- → 2012Q1
Comment 8•12 years ago
|
||
Tossing this into the 2012.6 sprint to look at dropping questions from the /questions page after 90 days. If I can get to it, I can get to it.
Whiteboard: u=contributor c=questions s=2012.5 p=2 → u=contributor c=questions p=2
Target Milestone: 2012Q1 → 2012.6
Comment 10•12 years ago
|
||
I think this is actually a user-facing thing and not a contributor-facing thing.
Whiteboard: u=contributor c=questions p=2 → u=user c=questions p=2
Comment 11•12 years ago
|
||
When I look at the /questions page, there are a bunch of different views of the questions. It's not obvious to me which views "hide threads that have no answers after 90 days" should apply to. List of views: * All * Unsolved * Solved * No Replies * My Contributions Should it apply to all the views for everyone?
Reporter | ||
Comment 12•12 years ago
|
||
Hi Will, they should be hidden from all the views. The effect should be like removing them from the DB without actually removing them (for reporting purposes). Thanks!
Comment 13•12 years ago
|
||
Passing this back to Ricky because he implemented it already. It should land soon.
Assignee: willkg → rrosario
Assignee | ||
Comment 14•12 years ago
|
||
Landed on prod: https://github.com/mozilla/kitsune/commit/639a92965516e0890a0eeea14e39778e1f6934f2
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.
Description
•