1. 13 Nov, 2018 1 commit
  2. 23 Jul, 2018 1 commit
    • Carlos Garnacho's avatar
      tracker-extract: Tag errored out files as to be ignored · d92476bf
      Carlos Garnacho authored
      The TrackerExtractPersistence stuff takes care of marking files as ignored
      whenever those trigger crashes. However for the files that simply error out
      we just add those to a runtime blacklist, which gets forgotten on next runs.
      Those will trigger message/warning logging each time tracker-extract is
      restarted, which is more often now. Just mark those as failures as it'd
      happen with files resulting in crashes. We need to think how these files
      are generically retried after extractor fixes/updates, but that is also
      missing for crashing files.
      Closes: #6
  3. 22 Jun, 2018 1 commit
  4. 14 Nov, 2017 1 commit
  5. 12 Sep, 2017 1 commit
  6. 11 Jul, 2017 1 commit
  7. 29 Jun, 2017 1 commit
    • Carlos Garnacho's avatar
      libtracker-miner: Add TrackerMinerProxy object · 9831c102
      Carlos Garnacho authored
      And shift all miner dbus handling from TrackerMiner. This object
      takes a TrackerMiner and implements the org.freedesktop.Tracker1.Miner
      interface for it on DBus.
      One notable difference in handling here is that libtracker-miner
      does not try to own DBus names anymore, that is left up to the caller.
      The registered object will be available on whatever dbus name the
      caller does register.
      For compatibility, all TrackerMiner implementations around have been
      made to request their usual name.
  8. 20 Nov, 2016 1 commit
  9. 14 Jul, 2016 2 commits
    • Sam Thursfield's avatar
      Use TrackerResource instead of TrackerSparqlBuilder in all extractors · 8cc026da
      Sam Thursfield authored
      For a long time, all the Tracker extractors have manually constructed a
      SPARQL update command using TrackerSparqlBuilder to represent their
      output. This commit changes all of them to use the TrackerResource
      class instead, which makes the code a lot more concise and readable.
      This introduces some API breaks in the internal libtracker-extract
      library. This has been a private library since Tracker 0.16 or earlier,
      so it's fine.
      If the extractors only output SPARQL then they are only useful to
      people who are using a SPARQL store. Now we can output a serialization
      format like Turtle as well. This will hopefully make the extract modules
      useful outside of Tracker itself.
      I've tried to preserve the behaviour of the extractors as much as
      possible, but there are two things that are now handled differently:
        * nao:Tag resources are given a fixed URI based on the tag label, such
          as <urn:tag:My_Tag>. Previously they were inserted as blank nodes,
          so tracker-store would give them unique IDs like <urn:uuid:1234...>
        * All extractors created nco:Contact resources for content publishers,
          but previously some would assign fixed URIs based on the name
          <urn:contact:James%20Joyce>, while others would insert them as blank
          nodes so they would be assigned unique IDs like <urn:uuid:1234...>.
          Now, all extractors create nco:Contact resources with fixed URIs
          based on the content creator's name.
    • Sam Thursfield's avatar
      tracker-extract: Fix invalid SPARQL used when blacklisting files · c0913abb
      Sam Thursfield authored
      This issue meant that files that triggered crashes never got
      blacklisted, as the invalid SPARQL was ignored by the tracker-store.
      So tracker-extract would spin on invalid files forever in some cases.
  10. 14 Mar, 2016 1 commit
    • Carlos Garnacho's avatar
      tracker-extract: Propagate urn to the TrackerExtractInfo · 389068a3
      Carlos Garnacho authored
      Now that extraction is performed after the file got initially
      inserted and has an URN, there's no reason we can't pass the
      URN to the TrackerExtractInfo. This would make URNs available
      to extract modules, which have some places where the SPARQL
      produced would be clearer.
      This actually opens the path for quite a cleanup, we might
      pass a single TrackerSparqlBuilder to extract modules instead
      of doing the postprocessing we currently perform.
  11. 11 Jan, 2016 1 commit
  12. 25 Nov, 2015 1 commit
  13. 15 Aug, 2015 1 commit
  14. 04 Aug, 2015 1 commit
  15. 01 Jul, 2015 2 commits
  16. 17 Mar, 2015 1 commit
  17. 24 Feb, 2015 1 commit
  18. 07 Dec, 2014 1 commit
  19. 27 Oct, 2014 1 commit
    • Martyn Russell's avatar
      libtracker-common: Moved tracker-ontologies.h into libtracker-sparql · a4d60c19
      Martyn Russell authored
      The Namespace has been cleaned up too, all APIs now start with:
      The well known definition for the TrackerMinerFS graph has also been changed
      because it now applies to more than just the TrackerMinerFS, we're using it
      It should probably be internal actually.
  20. 13 Aug, 2014 1 commit
    • Carlos Garnacho's avatar
      tracker-extract: Implement "failsafe" extraction · fa17f7a7
      Carlos Garnacho authored
      The extractor will store a symbolic link in a user directory in /tmp to
      the file(s) being currently processed, encoding also the number of tries
      previously performed. If the extractor happens to crash, the links will
      be used on a future respawn to resume operation.
      If enough crashes happen on a given file, the file will be then discarded,
      and tagged with an "extractor-failure-data-source" nie:dataSource,
      additionally to the dataSource that will make tracker-extract take the
      file as indexed in future runs.
  21. 21 Mar, 2014 1 commit
  22. 17 Mar, 2014 1 commit
  23. 14 Mar, 2014 1 commit
    • Martyn Russell's avatar
      tracker-extract: Improve logging, too many debug statements · 737755d6
      Martyn Russell authored
      It was hard to see what was going on with most logs as debug comments.
      Also all thread messages are now debug and have been moved into the #ifdef for
      other thread events
      It's a bit easier to see what is going on now using -v 2 and there is less
      mess with -v 3
  24. 20 Feb, 2014 4 commits
  25. 11 Feb, 2014 1 commit
  26. 06 Feb, 2014 1 commit
  27. 21 Jan, 2014 2 commits