There are tests which shows that a custom analyzer is used when adding to an index... and the "analyzer" config parameter can override the "type":"fulltext" parameter (in the SNAPSHOT version at least). So, code-wise, look at IndexType which instantiates a custom analyzer and use it for that index. Both during insertion and querying.
Tests: TestLuceneIndex#makeSureCustomAnalyzerCanBeUsed() TestLuceneIndex#makeSureCustomAnalyzerCanBeUsed2() 2010/10/28 David Montag <[email protected]> > Hi, > > When using the Lucene index, a custom Analyzer implementation can be > supplied in the config. It will only be used if it's a fulltext index. > > Here's my issue. I can't see where the analyzer is used when indexing a > node > or relationship. As far as I can tell, it's only used when querying the > fulltext index. Shouldn't indexing also make use of the analyzer? > > David > > -- > David Montag, Manager, Customer Support > Neo Technology, www.neotechnology.com > Cell: 650.556.4411 > [email protected] > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [[email protected]] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
