Doc length nomalization in Lucene LM

2016-07-21 Thread Dwaipayan Roy
​Hello, In *SimilarityBase.java*, I can see that the length of the document is is getting normalized by using the function *decodeNormValue()*. But I can't understand how the normalizations is done. Can you please help? Also, is there any way to avoid this doc-length normalization, to use the raw

Indexing and storing Long fields

2016-07-21 Thread Siraj Haider
Hi, We want to store and index a long value. Currently when we are adding two fields with same name, one is NumericDocValuesField and the other is StoredField. But it seems like the search is not returning any document when we query on that field, however we are able to retrieve the field values

Re: MmapDirectory and IndexReader reuse

2016-07-21 Thread Vladimir Kotal
On 07/18/16 05:52 PM, Uwe Schindler wrote: Hi, Have a separate searcher manager for every directory. On every incoming search request, fetch the actual DirectoryReaders from the searcher managers and build a MultiReader from it. This costs nothing, as MultiReader is just a thin wrapper where

Re: MmapDirectory and IndexReader reuse

2016-07-21 Thread Michael McCandless
Can't you pass your own SearcherFactory to SearcherManager to do that? Mike McCandless http://blog.mikemccandless.com On Thu, Jul 21, 2016 at 1:34 PM, Vladimir Kotal wrote: > On 07/18/16 05:52 PM, Uwe Schindler wrote: > >> Hi, >> >> Have a separate searcher manager for every directory. On ever

Re: Indexing and storing Long fields

2016-07-21 Thread Michael McCandless
Two different fields can be the same name. I think the problem is that you are indexing it as doc values, which is not searchable. To make your numeric fields searchable, use e.g. LongPoint (as of Lucene 6.0) or LongField (before 6.0). Mike McCandless http://blog.mikemccandless.com On Thu, Jul