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.

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

PatternAnalyzer should use PatternTokenFilter instead #6717

Closed
clintongormley opened this issue Jul 3, 2014 · 0 comments · Fixed by #6792
Closed

PatternAnalyzer should use PatternTokenFilter instead #6717

clintongormley opened this issue Jul 3, 2014 · 0 comments · Fixed by #6792
Assignees

Comments

@clintongormley
Copy link

The PatternAnalyzer in Lucene is deprecated and it should be implemented using the PatternTokenizer, LowerCaseFilter and StopTokenFilter instead.

Would fix the bug in #895

areek added a commit to areek/elasticsearch that referenced this issue Jul 9, 2014
Instead of using the PatternTokenizer, the functionality was replicated by using Lucene's StopFilter, PatterTokenizer and LowerCaseFilter

Closes elastic#6717
@s1monw s1monw added v1.3.0 and removed v1.4.0 labels Jul 9, 2014
areek added a commit that referenced this issue Jul 9, 2014
Instead of using the PatternTokenizer, the functionality was replicated by using Lucene's StopFilter, PatterTokenizer and LowerCaseFilter

Closes #6717
@clintongormley clintongormley changed the title PatternAnalyzer should use PatternTokenFilter instead Analysis: PatternAnalyzer should use PatternTokenFilter instead Jul 16, 2014
@clintongormley clintongormley added the :Search/Analysis How text is split into tokens label Jun 7, 2015
@clintongormley clintongormley changed the title Analysis: PatternAnalyzer should use PatternTokenFilter instead PatternAnalyzer should use PatternTokenFilter instead Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants