[ckan-dev] colorado.ckan.net search API not showing new package

[Allan Glen]

Sean,

What I found is that when I updated the package via the REST API (I updated
the version number) it started showing up in the search results.  It seems
like something was being cached and the cache was being invalidated when
updated via the REST API.

The problem can be reproduced by creating a package on
colorado.ckan.net(using the UI) and then searching for it via the
search API.

Thanks,
Allan


> Date: Mon, 19 Mar 2012 13:35:01 +0000
> From: Sean Hammond <sean.hammond at okfn.org>
> Subject: Re: [ckan-dev] colorado.ckan.net search API not showing new
>        package
> To: ckan-dev at lists.okfn.org
> Message-ID: <4F673605.1080700 at okfn.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> > I am one of the members involved in OpenColorado (using the
> > colorado.ckan.net instance) and I have noticed that after adding a
> package
> > that it does not show up in the search API.  Is there a caching issue
> > somewhere or some other reason why this would not show up?
> >
> > Here is the package:
> > http://colorado.ckan.net/api/rest/package/town-of-castle-rock-railroads
> >
> > It shows up using the REST API:
> > http://colorado.ckan.net/api/rest/group/castlerock
> >
> > But not using the search API:
> >
> http://colorado.ckan.net/api/2/search/package?groups=castlerock&order_by=rank&offset=0&limit=10&all_fields=1
>
> Hey Alan, is the problem resolved? I seem to be seeing the package in
> your search API now.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120321/0e5e8035/attachment-0001.html>