Re: StackOverflowError in ControlledRealTimeReopenThread.run

Hmm, the disturbing part of this stack trace is how many nested IndexReader.reportCloseToParentReaders there are: that's not right. It looks like you have deeply nested IndexReaders. Why did you need to use this WrappableSearcherManager? It seems to disable an important check from SearcherManage

QueryParser with CustomAnalyzer wrongly uses PatternReplaceCharFilter

I am using org.apache.lucene.queryparser.classic.QueryParser in lucene 6.0.0 to parse queries using a CustomAnalyzer as shown below: public static void testFilmAnalyzer() throws IOException, ParseException { CustomAnalyzer nameAnalyzer = CustomAnalyzer.builder() .addCharFilter("pa

Storing numeric fields in Apache 6

Hello all, I need to index some numeric fields, search with numeric range queries, and store the data to retrieve it afterwards. If I understand correctly, the recommended way to do this in Lucene 6 is with the DoublePoint/LongPoint/XxxPoint field types. I have already implemented this, extend

Storing numeric fields in Apache 6

Hello all, I need to index some numeric fields, search with numeric range queries, and store the data to retrieve it afterwards. If I understand correctly, the recommended way to do this in Lucene 6 is with the DoublePoint/LongPoint/XxxPoint field types. I have already implemented this, extend

Re: Storing numeric fields in Apache 6

If I'm right, you should use a StoredField to save the value, you can give it the same name as the used for the DoublePoint field. El jueves, 28 de abril de 2016, j.Pardos escribió: > Hello all, > > I need to index some numeric fields, search with numeric range queries, > and store the data to r

Re: Storing numeric fields in Apache 6

You should add a StoredField with the same name containing the value: doc.add(new DoublePoint(name, Double.parseDouble(value)); doc.add(new StoredField(name, Double.parseDouble(value)); Alan Woodward www.flax.co.uk On 28 Apr 2016, at 13:10, j.Pardos wrote: > Hello all, > > I need to index som

Re: QueryParser with CustomAnalyzer wrongly uses PatternReplaceCharFilter

Classic QueryParser splits on whitespace and then sends the chunks to the analyzer one at a time. See . -- Steve www.lucidworks.com > On Apr 28, 2016, at 5:54 AM, Bahaa Eldesouky wrote: > > I am using org.apache.lucene.queryparser.classic.Qu

RE: QueryParser with CustomAnalyzer wrongly uses PatternReplaceCharFilter

Hi, this is a general problem of using Analyzers in combination with QueryParser. Query Parsing is done *before* the terms are tokenized: QueryParser uses a JavaCC grammar to parse the query. This involves some query-parsing specific tokenization. Once the query parser has analyzed the syntax,

Re: Storing numeric fields in Apache 6

Thank you very much, and sorry for the double post. -Mensaje original- > De: "Alan Woodward" > A: java-user@lucene.apache.org > Fecha: 28/04/2016 14:30 > Asunto: Re: Storing numeric fields in Apache 6 > > You should add a StoredField with the same name containing the value: > > doc

Query Expansion for Synonyms

I'm investigating various ways of supporting synonyms in Lucene. One such approach that looks potentially interesting is to do a kind of "query expansion". For example, if the user searches for "us 1888", one might expand the query as follows: SpanNearQuery query = new SpanNearQuery

Re: Query Expansion for Synonyms

Hi Daniel, Since you are restricting inOrder=true and proximity=0 in the top level query, there is no problem in your particular example. If you weren't restricting, injecting synonyms with plain OR, sometimes cause 'query drift': injection/addition of one term changes result list drastically.