Or, a slightly uglier solution: if you are going to use that analyzer for all your fulltext indexing needs then you could modify the source of the index component (very small patch), build a jar and use that instead of the standard one. I attached an example patch (for neo4j-index 1.1).
2010/9/16 Mattias Persson <matt...@neotechnology.com> > I previously wrote that you could override LuceneFulltextIndexService and > assign your Analyzer there, but now I see that it can't be done there... > it's on a lower level. So as Peter pointed out, one option would be to go > with the new index framework where you can specify an analyzer at index > creation time (and perhaps be able to change it later, but currently the > code doesn't allow for that) and you'd be all set. > > 2010/9/15 <rick.bullo...@burningskysoftware.com> > >> Neo uses the StandardTokenizer by default (lowercase + whitespace). >> >> We think we found a way to use StandardTokenizer with the Apache Solr >> "HTMLStripReader" reader implementation to handle it, but we're having >> a tough time determining how best to extend/override neo's default >> tokenizer implementation, since there are no public methods or >> constructors which provide a means for overriding them. >> >> >> >> We're working with the neo team on it and as soon as we have an answer, >> I'll post it up here. >> >> >> >> Thanks! >> >> >> >> -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com
_______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
