Closed
Bug 768232
Opened 12 years ago
Closed 12 years ago
[ia] Add product field to wiki documents mapping (search index)
Categories
(support.mozilla.org :: Knowledge Base Software, task, P1)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2012.14
People
(Reporter: rrosario, Assigned: rrosario)
References
Details
(Whiteboard: u=user c=wiki p=1)
We need to be able to filter/query/facet documents by product. Once the database pieces are in place, we need to put this into the ES index. This means at least updating the `get_mapping() and `extract_document`.
Assignee | ||
Comment 1•12 years ago
|
||
Before doing this, we need to make sure we can facet on a list of strings (how we currently index tags, for example). Assuming we can, making this a 1pt. If there are limitations on faceting a list of strings, the pts will need to be adjusted accordingly.
Whiteboard: u=user c=wiki p=1
Comment 2•12 years ago
|
||
Faceting on lists of strings won't be a problem. For example: doc1 = tags ['a', 'b', 'c'] doc2 = tags ['a'] Faceting on the 'tags' field yields these counts: a - 2 b - 1 c - 1
Assignee | ||
Updated•12 years ago
|
Target Milestone: 2012Q3 → 2012.14
Comment 3•12 years ago
|
||
Adding [ia] to title.
Summary: Add product field to wiki documents mapping (search index) → [ia] Add product field to wiki documents mapping (search index)
Updated•12 years ago
|
Priority: -- → P1
Comment 5•12 years ago
|
||
This is more involved. 1. add the field to the mapping 2. add the extraction code which pulls from products and adds to the mapping However, by the time we're working on this bug, the code it relies on is using the new product system. Thus, we need to finish it off: 3. update the search views to use the product field rather than the tags field for wiki documents
Assignee | ||
Comment 6•12 years ago
|
||
willkg, can I grab this to do it together with the mapping changes for topic? It would be one less mapping change and reindex dance.
Comment 7•12 years ago
|
||
You're right, but this depends on the product stuff, not the topic stuff. So if you do it, you still have to land this with the migration product changes.
Assignee | ||
Comment 8•12 years ago
|
||
Grabbing to do it with topics and I have the itch. It will need to wait until the blockers land before landing though but I will have the commit ready.
Assignee: willkg → rrosario
Assignee | ||
Comment 9•12 years ago
|
||
This is in a pull request that needs a little more work: https://github.com/mozilla/kitsune/pull/741
Assignee | ||
Comment 10•12 years ago
|
||
This landed on master: Part 1: https://github.com/mozilla/kitsune/commit/599551e13092de60a5755e4383376bab048edaff Part 2: https://github.com/mozilla/kitsune/commit/ee2f2f21fbb4f46f982b51aba768d399c3d09d04 Now I am doing the 2 step deploy to stage. If that works, it goes to prod after.
Assignee | ||
Comment 11•12 years ago
|
||
Landed my first index mapping change on prod \o/
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
•