Bug 460311 - Errata Search: searching for 'apache' results in unrelated results
Summary: Errata Search: searching for 'apache' results in unrelated results
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 0.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Matthews
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space04
TreeView+ depends on / blocked
 
Reported: 2008-08-27 14:24 UTC by Justin Sherrill
Modified: 2009-01-12 19:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-12 19:21:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Justin Sherrill 2008-08-27 14:24:31 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:


   1. Login to RHN
   2. Make sure RHN is populated w/ systems and errata and have the Red Hat Enterprise Linux AS (v. 4 for 32-bit x86) channel synced
   3. Navagate to "Errata" on the main navigation bar
   4. Navagate to "Advanced Search" on the left pane menu
   5. The "Erratum Search" page should appear
   6. In the search box, type "apache"
   7. Make sure "All Fields" are selected in the "what to search for box"
   8. Click "search" 
  
Actual results:

Errata "RHBA-2007:0712" is included which is a cachefilesd errata and doesn't have anything to do with apache.

Expected results:
Only errata related with apache (httpd) would be present




Not sure if the scores need to be trimmed, but I wouldn't think this should be returned.

Comment 1 John Matthews 2009-01-12 19:21:53 UTC
This matches because "cachefilesd"  is close to "apache"

Notice cache and apache both share "ache".

The search server is using NGrams for searching which allows flexibility on spelling, therefore hits like this will show up.

The hits returned are ordered by score, so the better matches will be higher on the return list.


Note You need to log in before you can comment on or make changes to this bug.