Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LuceneSearchService - normalizeSearchTerm should allow leading wildcard #331

Closed
rsoika opened this issue Dec 7, 2017 · 0 comments
Closed

LuceneSearchService - normalizeSearchTerm should allow leading wildcard #331

rsoika opened this issue Dec 7, 2017 · 0 comments
Labels
enhancement testing
Milestone
4.2.4

Comments

@rsoika
Copy link
Member

rsoika commented Dec 7, 2017

The method normalizeSearchTerm must allow leading wildcards

parser.setAllowLeadingWildcard(true);

This is alreay supported by the serach method but not in the method normalizeSerachTerm which forces a unexpected exception and avoid wildcard searches with leading wildbards

Example:

*solutions

search for 'Imixs Softwaresolutions'
@rsoika rsoika added this to the 4.2.4 milestone Dec 7, 2017
rsoika added a commit that referenced this issue Dec 7, 2017
@rsoika
fixed
8b3c873 
issue #331
@rsoika rsoika added the testing label Dec 7, 2017
@rsoika rsoika closed this as completed Dec 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement testing
Projects
None yet
Milestone
4.2.4
Development

No branches or pull requests
1 participant
@rsoika