Gesendet: Dienstag, 26. Oktober 2010 13:34
An: Neo4j user discussions
Betreff: Re: [Neo4j] LuceneIndexProvider EXACT_CONFIG vs. FULLTEXT_CONFIG
I just found the problem... fulltext defaults to being case-insensitive (by
converting added values as well as string queries to lower case). There's
: Dienstag, 26. Oktober 2010 13:34
An: Neo4j user discussions
Betreff: Re: [Neo4j] LuceneIndexProvider EXACT_CONFIG vs. FULLTEXT_CONFIG
I just found the problem... fulltext defaults to being case-insensitive (by
converting added values as well as string queries to lower case). There's a
quirk
I just found the problem... fulltext defaults to being case-insensitive (by
converting added values as well as string queries to lower case). There's a
quirk in the Lucene QueryParser where you must specifically set whether or
not range/wildcard queries should have their terms converted into lower
Oh yeah, that's right... you can control it via to_lower_case property in
the config. F.ex. you could do your own fulltext config like this:
MapString, String caseSensitiveFulltextConfig = new HashMapString,
String( FULLTEXT_CONFIG );
caseSensitiveFulltextConfig.put( to_lower_case, false
4 matches
Mail list logo