RE: Lucene parsing overhead VS directly creating queries?

Hi, The overhead is neglectible in most cases. The real reason why you want to create queries on your own is that you have all control: - if you have (unanalyzed) StringField and want to query them, it is better to build queries by hand. This is mostly the case for special data types or facet

Lucene parsing overhead VS directly creating queries?

Hi Is there any performance gain of writing Lucene queries (query objects) rather than parsing Lucene query strings using QueryParser. I believe parser has its own overhead. Example: Term lTerm1 = new Term("rs", "997101"); Term uTerm1 = new Term("rs", "997104"); TermRangeQuery trQuery1 =

Performance of Prefix, Wildcard and Regex queries?

Hi Performance of Prefix, Wildcard and Regex queries? Does Lucene internally optimizes this (using rewrite or something else) or I have to manually create specific queries depending on input pattern. Example if input is 78* create Prefix query if input is 87?98* create Wildcard query if input is

Creating Queries agnostic to Lucene Versions

Hi How can I make my Lucene queries agnostic to Lucene Versions? e.g. NumericRangeQuery in 5.3.1 is LegacyNumericRangeQuery in 6.0.0 (NumericRangeQuery is completely removed) -- Rajnish

Re: Lucene Query Parser Special Characters

The documentation I'm referencing is here: https://lucene.apache.org/core/4_5_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description, with a note: org.apache.lucene.queryparser.flexible.standard

Re: Default LRUQueryCache causing OOO exception

Thank you for bringing closure! Mike McCandless http://blog.mikemccandless.com On Fri, Oct 14, 2016 at 2:41 AM, Rahul Chandwani wrote: > Thanks Adrien, Micheal, Trejkaz. > > > You guys were right. > > I was concentrating my energy at wrong place. > > We have two types of indexes: > > 1. File b