Feature #10596: Search should default to partial matching - Katello - Foreman

Actions

Copy link

Feature #10596

closed

Search should default to partial matching

Added by Roy Williams about 9 years ago. Updated almost 6 years ago.

Status:

Rejected

Priority:

Low

Assignee:

Category:

Target version:

Katello Recycle Bin

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Currently when searching hosts or content, you are required to use globbing or wildcards to make matches. It should default to partial string matching unless quotations are provided.

I am not sure how difficult this would be implement but as it stands searching for "raven" when entries raven1,raven2,raven3 exist will result in nothing being shown when it should show the partial matches. I believe to be that explicit should require quoting.

Actions

Copy link

Updated by Roy Williams about 9 years ago

Can someone move this issue into category of search?

Actions

Copy link

Updated by Dominic Cleal about 9 years ago

Which page are you searching on precisely? Foreman should already do this.

Actions

Copy link

Updated by Roy Williams about 9 years ago

Within "Hosts -> All Hosts" and within the Product Repositories. It doesn't seem to do partial matching under Satellite 6.0.8 and Katello I'm required to use globs to make it match.

so for the case of raven1 I need to use 'raven*' in the search window.

Actions

Copy link

Updated by Dominic Cleal about 9 years ago

Project changed from foreman-tasks to Katello
Triaged set to No

Moving to Katello for a fix for the repos page then, Foreman's hosts page already does this. If you can reproduce against a supported version, please file a new bug with debug logs, thanks.

Actions

Copy link

Updated by Roy Williams about 9 years ago

Dominic this is occurring with Satellite 6.0.8 as well....

Actions

Copy link

Updated by Eric Helms about 9 years ago

Triaged changed from No to Yes

This is a result of the two separate search backends that we currently use -- ActiveRecord w/ scoped search and Elasticsearch. The latter is being phased out and removed which will unify searching and address this issue. We can keep this open if you wish for tracking, but we won't address a fix for this directly other than our larger removal of Elasticsearch.

Actions

Copy link

Updated by Roy Williams about 9 years ago

Thanks Eric,

I understand so this is getting changed through that process I just wanted to make sure this was getting fixed by some measure. You can close this issue if you want I wasn't sure there was anything being done.

Actions

Copy link