Re: Custom indexing

Hi, Please try letter tokenizer, it should cover your example. Ahmet On Monday, April 18, 2016 3:02 PM, PK C wrote: Hi, Thank you very much for your quick responses. Jack Krupansky, The main use case is searching in file names. For example, lucene.txt,

Re: Problem with NGramAnalyzer, PhraseQuery and Highlighter

Hi Eva, This looks like a bug in WeightedSpanTermExtractor, which is rewriting your PhraseQuery into a SpanNearQuery without checking how many terms there are. Could you open a JIRA ticket? Alan Woodward www.flax.co.uk > On 18 Apr 2016, at 16:27, Eva Popenda wrote: >

Problem with NGramAnalyzer, PhraseQuery and Highlighter

Hi, I have a problem when using the Highlighter with N-GramAnalyzer and PhraseQuery: Searching for a substring with length = N (4 in my case) yields the following exception: java.lang.IllegalArgumentException: Less than 2 subSpans.size():1 at

Combining many field as JSON and made it into a single field - Performance

I tried to combine multiple different fields (Stored Fields) into a JSON object and added in to lucene document as single field I get a better performance while reading the field from the index. though constructing the JSON requires additional time, It still retrieve the data faster What

Re: Custom indexing

You failed to disclose up front that you are using such an old release of Lucene. Lucene is now on 6.0. I'll defer to others if they wish to provide support for such an old release. -- Jack Krupansky On Mon, Apr 18, 2016 at 8:01 AM, PK C wrote: > Hi, > >Thank you

Re: Custom indexing

Hi, Thank you very much for your quick responses. Jack Krupansky, The main use case is searching in file names. For example, lucene.txt, lucene_new.txt, lucene_1_new.txt. If I use 'lucene', I need to get all 3 files. with 'new' I need to get last two files. Please note that Standard