https://bugs.kde.org/show_bug.cgi?id=438434
--- Comment #17 from tagwer...@innerjoin.org --- (In reply to Martin Steigerwald from comment #15) > What for does Baloo need an invariant for the file? As I understand it... internally, it is the key within the index. It also allows "missed changes" to be reconciled if baloo is not running when the file is changed or has missed the inotify. > Why wouldn't a rename mess things up without an invariant (device number > or filesystem id)? Or otherwise put how would having device/filesystem > unique invariant help with a rename? I think "the trap" is to avoid reindexing everything in a large folder tree if you rename the top foldername. You need a way to tell if oldtree/x/y/z is the same file as newname/x/y/z or not... >From my experience, baloo has to react to inotify events and also be able to smoothly recover/catch up if the events are missed. > ... I bet you'd need a file/directory based > invariant for that. I.e. a hash value for each file ... Baloo also allows you to index the filename/metadata and not index the content. A hash would be extra work here... -- You are receiving this mail because: You are watching all bug changes.
