[ https://issues.apache.org/jira/browse/LUCENE-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275858#comment-14275858 ]
Robert Muir commented on LUCENE-6177: ------------------------------------- +1 to the patch! > Add CustomAnalyzer - a builder that creates Analyzers from the factory classes > ------------------------------------------------------------------------------ > > Key: LUCENE-6177 > URL: https://issues.apache.org/jira/browse/LUCENE-6177 > Project: Lucene - Core > Issue Type: New Feature > Components: modules/analysis > Reporter: Uwe Schindler > Assignee: Uwe Schindler > Fix For: 5.0, Trunk > > Attachments: LUCENE-6177.patch, LUCENE-6177.patch > > > I prepared some "generic Analyzer class {{CustomAnalyzer}}, that makes it > easy to build analyzers like in Solr or Elasticsearch. Under the hood it uses > the factory classes. The class is made like a builder: > {code:java} > Analyzer ana = CustomAnalyzer.builder(Path.get("/path/to/config/dir")) > .withTokenizer("standard") > .addTokenFilter("standard") > .addTokenFilter("lowercase") > .addTokenFilter("stop", "ignoreCase", "false", "words", "stopwords.txt", > "format", "wordset") > .build(); > {code} > It is possible to give the resource loader (used by stopwords and similar). > By default it tries to load stuff from context classloader (without any class > as reference so paths must be absolute - this is the behaviour > ClasspathResourseLoader defaults to). > In addition you can give a Lucene MatchVersion, by default it would use > Version.LATEST (once LUCENE-5900 is completely fixed). -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org