I think this is how StandardTokenizerFactory works, if you want different
behavior, you should try to use a different tokenizer, also like Upayavira
said,use the analysis tab on the admin UI to see what analysis is doing to your
terms.
2015-10-26 12:33 GMT-07:00 Brian Narsi :
> That is right Ray,
That is right Ray, that is exactly what I found out and that is why I am
asking the question.
On Mon, Oct 26, 2015 at 2:19 PM, Ray Niu wrote:
> I found the conf minGramSize="2"，which will only create index with at least
> 2 chars，j will not match
> also StandardTokenizerFactory will tokenize st
I found the conf minGramSize="2"，which will only create index with at least
2 chars，j will not match
also StandardTokenizerFactory will tokenize st j to st and j
2015年10月26日星期一，Brian Narsi 写道：
> I have the following field type on a field ClientName:
>
> positionIncrementGap="100">
>
>
>
> m
Use the analysis tab on the admin UI to see what analysis is doing to
your terms.
Then bear in mind that a query parser will split on space. So, you might
want to do clientName:"st ju me" to make the tokenisation happen within
the analysis chain rather than the query parser.
Upayavira
On Mon, Oc
I have the following field type on a field ClientName:
For data where
ClientName = st jude medical inc
When querying I get the following:
1) st --> result = st jude medical inc (works correctly)
2) st j --> No results are returned (NOT correct) - Expect to find st jude
medical i
