Bug 805324
Summary: | Lucene syntax for searches in promotion section is not working correctly | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> |
Component: | WebUI | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED ERRATA | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | cpelland, cwelton, hbrock, jsherril, mmccune |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-15 18:57:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Og Maciel
2012-03-20 21:28:11 UTC
Note to self: In app controller (working correctly) we do: !AppConfig.simple_search_tokens.any?{|s| search.downcase.match(s)} but in promotion packges (not working) we do: AppConfig.simple_search_tokens.any?{|s| !query_down.match(s)} notice the swap of the ! char katello commit 30be04bc75a004987bf3ed5bc063fd8cce36fb8d few changes here: Change to use default field instead of analysing if the user used a special char or not. Made package name be a keyword analyzed field. Created new field for auto complete called 'name_autocomplete' that is analyzed with the special ngramming made for auto complete. Improved autocomplete to do a maximum of 20 grams (up from 10). QA Verified using a google chrome repo Search for "goo" returns nothing Search for "goo*" returns valid results Search for "goo " returns nothing Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0665.html |