Closed
Bug 940361
Opened 11 years ago
Closed 10 years ago
response counts for a locale in sidebar change when you select the locale
Categories
(Input Graveyard :: Dashboard, defect)
Input Graveyard
Dashboard
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=user c=dashboard p=1 s=input.2014q4)
The summary is rubbish, but the gist of it is this: 1. go to https://input.mozilla.org/ 2. look at the locale section of the sidebar on the left 3. for each locale look at the response count for that locale, then select the locale and then look a the response count again For most of them, the two numbers will be the same. However, for some it's different. For example, right now if I look at Spanish, the general number is 153, but if I select it, then I see 235. Further, the total number of responses in the upper right hand corner also says 235. All the other locales work fine. Issue was discovered while writing tests. Comments here: https://github.com/mozilla/input-tests/pull/156#issuecomment-28788870
Assignee | ||
Comment 1•10 years ago
|
||
Tossing this in the 2013q4 sprint to look into.
Whiteboard: u=user c=dashboard p= s=input.2013q4
Assignee | ||
Comment 2•10 years ago
|
||
This is not right, but not a big big deal. It's entirely possible it's caching-related or something like that. I'm going to push it off to next quarter.
Whiteboard: u=user c=dashboard p= s=input.2013q4 → u=user c=dashboard p= s=input.2014q1
Comment 4•10 years ago
|
||
Will: should we xfail the failures associated with this bug, so we can get coverage on production working?
Assignee | ||
Comment 5•10 years ago
|
||
xfailing it now is fine. I'm pretty sure I listed a bunch of options in the bug comments or the pull request.
Assignee | ||
Comment 6•10 years ago
|
||
I bet the problem is this: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-terms-facet.html#_accuracy_control That sure seems likely. If we adjust the size, that should fix it.
Assignee | ||
Comment 7•10 years ago
|
||
I'm 99% sure it's the size thing. We're upgrading to Elasticsearch 0.90.10 soon. Along with that, I'll push out a new version of ElasticUtils. Once we update to that, we can specify a bigger size and that should fix this. Moving this to 2014q2.
Whiteboard: u=user c=dashboard p= s=input.2014q1 → u=user c=dashboard p= s=input.2014q2
Assignee | ||
Comment 8•10 years ago
|
||
I nixed the test, so I'm going to push this off indefinitely.
Whiteboard: u=user c=dashboard p= s=input.2014q2 → u=user c=dashboard p= s=
Assignee | ||
Comment 9•10 years ago
|
||
Talked with Ricky about a similar issue with SUMO and decided to just go fix it for Input. Grabbing this and fixing it now.
Assignee: nobody → willkg
Whiteboard: u=user c=dashboard p= s= → u=user c=dashboard p=1 s=input.2014q4
Assignee | ||
Comment 10•10 years ago
|
||
In a PR: https://github.com/mozilla/fjord/pull/366 I can't verify the fix until we verify the STR are still true in production, then deploy this, then re-check to see if the problem went away. I'll do that when I push this to production and report back whether it fixed it or not.
Assignee | ||
Comment 11•10 years ago
|
||
Erik pointed out we should probably use "shard_size" instead of "size". I created bug #1082152 for that since ElasticUtils doesn't support it, so the fix is harder to do.
Assignee | ||
Comment 12•10 years ago
|
||
Landed in master: https://github.com/mozilla/fjord/commit/a9bf3b139d9a950f0aa1aad399c4f02a21ed6ce8
Status: NEW → ASSIGNED
Assignee | ||
Comment 13•10 years ago
|
||
Bah. I missed my deployment window. This will have to wait to go to prod until Monday.
Assignee | ||
Comment 14•10 years ago
|
||
Pushed this to prod just now. I'll verify it later.
Assignee | ||
Comment 15•10 years ago
|
||
I went through all the locales and the number on the front page matches the number after filtering on that locale. So I think this is good now. Marking as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•