After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764783 - Warning: Could not create FTS delete statement: table fts5 has no column named nco:hobby
Warning: Could not create FTS delete statement: table fts5 has no column name...
Status: RESOLVED DUPLICATE of bug 764737
Product: tracker
Classification: Core
Component: FTS
1.8.x
Other All
: Normal normal
: ---
Assigned To: tracker-general
tracker-general
Depends on:
Blocks:
 
 
Reported: 2016-04-08 13:51 UTC by Christian Stadelmann
Modified: 2016-05-07 19:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Stadelmann 2016-04-08 13:51:25 UTC
I am getting this warning quite often, and Torben Andresen [1] is, too.

Full warning:

org.freedesktop.Tracker1[1773]: (tracker-store:2119): Tracker-WARNING **: Could not create FTS delete statement: table fts5 has no column named nco:hobby

This warning started occurring after a full tracker database initialization was done and isn't connected (meaning: is no direct result of) any user interaction.

As with [2] those warnings are useless without a file path. Please make the warning more specific or don't warn at all.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=764737#c1
[2] https://bugzilla.gnome.org/show_bug.cgi?id=764740
Comment 1 Carlos Garnacho 2016-05-05 15:46:50 UTC
This warning means that the tracker 1.6 (using FTS4) -> 1.8 (using FTS5) transition hasn't been that smooth for your case...

In order to trigger the change in 1.8, there had to be an ontology change so FTS tables are recreated with the new version. I chose removing that "nco:hobby" property from being fulltext-indexed.

So it seems that on one hand your tracker database was successfully updated to FTS5, and that property is effectively non-fts. But OTOH, tracker seems to internally think the property is still fts, and thus the warnings.

Could you paste the output of:

tracker info http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby

It should have no traces of the tracker:fulltextIndexed property, although I suspect it does. In that case I'm mostly sure that running the following command once would remove the warning for good:

tracker sparql -u -q "DELETE { <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby> tracker:fulltextIndexed ?any } WHERE { <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby> tracker:fulltextIndexed ?any }"

Nonetheless would be great to know why didn't this happen automatically, as it should have been the case when modifying the database in response to the ontology changes.
Comment 2 Carlos Garnacho 2016-05-07 15:32:26 UTC

*** This bug has been marked as a duplicate of bug 764737 ***
Comment 3 Christian Stadelmann 2016-05-07 19:42:27 UTC
(In reply to Carlos Garnacho from comment #1)
> This warning means that the tracker 1.6 (using FTS4) -> 1.8 (using FTS5)
> transition hasn't been that smooth for your case...
> 
> In order to trigger the change in 1.8, there had to be an ontology change so
> FTS tables are recreated with the new version. I chose removing that
> "nco:hobby" property from being fulltext-indexed.
> 
> So it seems that on one hand your tracker database was successfully updated
> to FTS5, and that property is effectively non-fts. But OTOH, tracker seems
> to internally think the property is still fts, and thus the warnings.

I deleted this database after upgrading from Fedora 23. No reason for any transition.

> Could you paste the output of:
> 
> tracker info http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby

How should I do that? I have no clue of how tracker works.

> It should have no traces of the tracker:fulltextIndexed property, although I
> suspect it does. In that case I'm mostly sure that running the following
> command once would remove the warning for good:
> 
> tracker sparql -u -q "DELETE {
> <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby>
> tracker:fulltextIndexed ?any } WHERE {
> <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hobby>
> tracker:fulltextIndexed ?any }"

Should I still do that?