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
Hello,
I'm giving the new LuceneIndexProvider a trial und try to become acquainted
with EXACT_CONFIG and FULLTEXT_CONFIG. Currently, I do not understand some
differences between their quering-results..
For example:
String nameArnold = Arnold Aronson;
String key =
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
Hi,
could someone please explain me when to use EXACT_CONFIG and when
FULLTEXT_CONFIG when using the nodeIndex() of the LuceneIndexProvider?
It seems to me that one cannot execute wildcard searches in
FULLTEXT_CONFIG mode, it only works when EXACT_CONFIG is used. But what
is actually exact
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
6 matches
Mail list logo
