Bug 831569
Summary: | blog example search error searching for a stoplist word | ||
---|---|---|---|
Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Marek Schmidt <maschmid> |
Component: | Examples, Seam, HibernateSearch | Assignee: | Karel Piwko <kpiwko> |
Status: | CLOSED DEFERRED | QA Contact: | Karel Piwko <kpiwko> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.0.0.ER8 | CC: | bsutter, mnovotny, rruss, sanne |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | Seam2.3 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-19 08:18:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marek Schmidt
2012-06-13 10:33:13 UTC
That probably needs some help from HSearch devs, Sanne, could you help what is required to eliminate that exception with stoplist words? The business logic could validatethe search input is containing something which is not empty after analysis and show a message to the user about how correct input should be. For a helper to see the tokenized input see: org.hibernate.search.util.AnalyzerUtils.tokenizedTermValues(Analyzer, String, String) Otherwise, we might think of changing the API a little bit to make this simpler; we could throw a subtype of SearchException instead, to make it easier to catch this problem specifically rather than asking business logic to pre-check. As a future usability improvement: https://hibernate.onjira.com/browse/HSEARCH-1161 |