Sorry, but you can only use a wildcard on a single term. "C0001.DevNm001"
gets indexed as two terms, "c0001" and "devnm001", so your wildcard won't
match any term (at least in this case.)
Also, if your query term includes a wildcard, it will not be fully analyzed.
Some filters such as lower ca
This is a follow up to the earlier thread I started to understand memory
usage patterns of SegmentReader instances, but I decided to create a
separate post since this issue is much more serious than the heap overhead
created by use of stored field compression.
Here is the use case, once again. The
CALL FOR PARTICIPATION
The 12th International Workshop on Java Technologies for
Real-time and Embedded Systems - JTRES 2014
October 13th - 14th
Niagara Falls, NY, USA
http://jtres2014.
I just wrote this small test case. Do you mean add some more field values
and search for it? I added a whole bunch of strings with the same
pattern. C000x.DevNm00y, changing the x and y values to different numbers.
I changed the code to add some similar and different patterns and this is
what I
Can you Post the Result of the queryparser for the other queries too?
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
Von: Milind
Gesendet: Dienstag, 26. August 2014 18:24
An: java-user@lucene.apache.org
Antwort an: java-user@lucene.apache.org
Betreff: Why does this search fail
I have a field with the value C0001.DevNm001. If I search for
C0001.DevNm001 --> Get Hit
DevNm00* --> Get Hit
C0001.DevNm00* --> Get No Hit
The field gets tokenized on the period since it's surrounded by a letter
and and a number. The query gets evaluated as a prefix query.
