FTS doesn't work properly with *Subject groupings
Bug #947835 reported by
Michal Hruby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
High
|
Michal Hruby |
Bug Description
Currently FTS is only approximating results when any of the *Subject groupings are used. This means that asking FTS for 20 most recent subjects containing "a" can right now return anything between 1 and 60 different subjects all depending on the order of recent events.
The idea here is to use xapian's collapse key functionality to be able to get rid of this approximation while doing performance and memory requirement measurements of its impact.
Related branches
lp:~rainct/zeitgeist/collapse-uri
- Michal Hruby (community): Needs Fixing
-
Diff: 115 lines (+37/-1)2 files modifiedextensions/fts++/indexer.cpp (+33/-1)
extensions/fts++/indexer.h (+4/-0)
Changed in zeitgeist: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Michal Hruby (mhr3) |
Changed in zeitgeist: | |
status: | In Progress → Fix Committed |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Adding massif profiles where one is current FTS and the other does the collapsing (using md5-hashes the uris, see RainCT's branch)