Ticket #324 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

Search indexing using notifications

Reported by: dread Owned by: dread
Priority: blocker Milestone: v1.1
Component: ckan Keywords:
Cc: pudo Repository:

Description (last modified by dread) (diff)

Currently search indexing is triggered directly using a Postgresql db callback. Now take advantage of the Notification system to register interest in all package changes and db changes to trigger this instead.

The indexing shall run in a separate shell/process, managed by supervisord.

Change History

comment:1 Changed 4 years ago by pudo

  • Cc pudo added

I am currently writing a Solr subclass for the search index (#317) and would propose adding standard methods to the ckan.libn.search.Search class: index_package(), index_tag(), index_group(). Those could then be called by a generic queue consumer, irrespective of the used search back-end. I will prototype such a consumer soon, so we should talk to avoid doing some duplicate work here.

comment:2 Changed 4 years ago by dread

  • Description modified (diff)

comment:3 Changed 4 years ago by dread

  • Status changed from new to closed
  • Resolution set to fixed

Done in changesets leading up to cset:ca565562129d.

Note: See TracTickets for help on using tickets.