On Wed, Sep 28, 2016 at 10:22 PM, Christoph Cullmann <cullm...@absint.com> wrote:
> Hi, > > > Generally speaking, in terms of Plasma feedback, Baloo doesn't come up > > /that/ much. > > I'm sure there's stuff in the bug tracker, but we don't have the big > public > > problem that we used to have. > > > > I think your problems are exagerrated because of the NFS mount. > > > > The only problem we have is the runner bringing down the shell when we > have > > the corrupt database - and from the comments above, that should be > > catchable. > You can catch that, by rewriting all current code, as there is no error > handling, > but yes, that is true. One can write lmdb code that handles corrupted DBs > and > catch all error cases. lmdb is no bad database in that aspect. > > > > > > -------- > > > > > Questions: > > > > Tracker doesn't look at xattrs at all. > > > > At which point we would need to think about migration. > > > > This is possibly solvable with a patch in tracker. The tracker maintainer > > (in 2014) sounds like he would be in support of it: > https://mail.gnome.org/ > > archives/tracker-list/2014-September/msg00045.html > > and there is a writeback module in tracker. > A one way migration would be to write a tracker "miner" (if don't use the > wrong word) > and move the tags into the tracker tag db, or what you cite above. > > Have you tried using tags in tracker? Using tracker-needle, and adding a tag I get: Could not update tags GDBus.Error.freedesktop.Track1.Sparql.Internal no such column: nie:DataObject1.ID Even after wiping the database. Same for using "tracker tag -a" Am I missing a package? David
