Full-text search in the find endpoint

Bug #1906804 reported by Francisco Jimenez Cabrera
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
Fix Committed
Hasan Ammar

Bug Description


This issue has been mentioned in our Charmhub dev weekly meeting.

Currently, when we use the find endpoint in the charmhub.io website, it's not searching for properties that we think are relevant.

As an example, the charm postgresql-k8s contains the world "kubernetes" in the summary and the description:

These properties are not being used for searches:

Apparently right now is only searching by author name and package name, we think it should include the summary, the description and the platforms where the package is available.

Thank you.

description: updated
Revision history for this message
Bret Barker (noise) wrote :

I believe this is fixed and deployed to staging thus far, see:


Changed in snapstore-server:
importance: Undecided → Medium
assignee: nobody → Hasan Ammar (hasanammar)
Revision history for this message
Daniel Manrique (roadmr) wrote :

Once the change is deployed we need to trigger "reindexing" of charms (and affected snaps), which is a simple database operation. Can be done on production today or early next week.

Changed in snapstore-server:
status: New → Fix Committed
Revision history for this message
Toto Bille (tbmb) wrote :


The search in the new indexes works well. \o/

Next step would be to have the possibility to search through architectures, platforms etc. via the same mechanism.

So as a user I can go on charmhub.io and search for kubernetes, without having to play around with filters, and get a list of charms that are related to kubernetes (extracted from their description, platform, name or else)

Revision history for this message
William Grant (wgrant) wrote :

It definitely doesn't make sense for full-text search to include the platform in general, but some other mechanism may be able to be devised.

Revision history for this message
Toto Bille (tbmb) wrote :

this is a feature that would be mostly for the website as far as I am concerned. I am not sure about the "discoverability feature" that juju provides (juju find?).

Having a flag that would allow us to extend the search to a wider range of field would be fine.

Revision history for this message
Bret Barker (noise) wrote :

I agree with William, a platform filter may make sense but not as part of the full-text search. There's a difference between looking for charms that are deployable to k8s vs charms for deploying kubernetes itself, so I'm not quite clear what the intent is for that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.