Bug 208596

Summary: keep a clean Nepomuk store (automatically purge redundant data)
Product: [Unmaintained] nepomuk Reporter: uetsah <uetsah>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED FIXED    
Severity: wishlist CC: tassilo, trueg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description uetsah 2009-09-26 13:53:08 UTC 
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Unlisted Binary Package

I get the feeling my Nepomuk store size is only growing and growing...

When deleting previously indexed files, and when adding new Strigi index exclude filters in the Nepomuk configuration, the Nepomuk store should properly shrink to exactly the same state as if .kde/share/apps/nepomuk/repository were deleted and everything re-indexed from scratch.
Comment 1 Sebastian Trueg 2009-09-28 12:03:02 UTC 
Deleting previously indexed files should already be handled. The size of the db, however, is no good indicator. It ca fluctuate based on internal states.
It would be better to test like this:

sopranocmd --model main --dbus org.kde.NepomukStorage list "<file:///home/me/path/to/a/deleted/file>

Also be aware that removed files are only picked up at the next big sweep, not immedeately.

Could you please test the above.
Comment 2 uetsah 2009-09-28 17:12:26 UTC 
Okay, I can confirm that according to the sopranocmd command deleting previously indexed files does in fact remove the corresponding data in the index.

However, so far I can't see any effect of removing an entry from the exclude filters list. (Is there any way to manually force one of those "big sweps"?)
Comment 3 Sebastian Trueg 2009-09-29 14:30:24 UTC 
To update all folders call:

qdbus org.kde.nepomuk.services.nepomukstrigiservice /nepomukstrigiservice org.kde.nepomuk.Strigi.updateAllFolders
Comment 4 Sebastian Trueg 2010-02-24 12:26:27 UTC 
This is done automatically on config change now.