JTRES 2016 Call For Papers

== CALL FOR PAPERS The 14th Workshop on Java Technologies for Real-Time and Embedded Systems JTRES 2016 Part of the

Re: Difference in Retrieving values of a docvalue field using atomicreader over duplicate StoredField

Well, each access may involve disk seeks (if the pages are not already hot in the OS's IO cache). So if you do some doc values + some stored fields you're looking at multiple seeks per docID you retrieve. Really you should only do this for a few hits, e.g. one page worth. Mike McCandless http:/

Difference in Retrieving values of a docvalue field using atomicreader over duplicate StoredField

Hi All, In javadoc of every docvalue field , there is line like ​ > If you also need to store the value, you should add a separate StoredField >

RE: analyzers-common VS analyzers-icu

That package has an ICU tokenizer and the ICUFoldingFilter. The ICUFoldingFilter does advanced (well, Unicode compliant) case folding/lowercasing/normalization and is critical for non-ascii languages. You can use that in place of the AsciiFoldingFilter and the LowerCaseFilter, and it should

analyzers-common VS analyzers-icu

Hi, I recently setup my code to choose the appropriate analyzer from analyzers-common depending on the language of the user's index/field. I then extended the existing source code to allow, for any language, to turn on/off things like stemming, case sensitivity, etc. Today I discovered ana

Re: Drawbacks of using Docvalues Fields

You can tell very little about performance with 50 documents, so I wouldn't trust these results at all. In particular I'm pretty sure that your search speed will suffer _greatly_ as you get more and more documents in your corpus if you use only DocValues but don't have indexed="true" set. Best, E

AW: Leftover write.lock file

Hi, > Never mind, folks. Just found an answer: > http://www.gossamer-threads.com/lists/lucene/java-user/110708 > > ... > > I am new to lucene. I was following the example, IndexFiles, from the > > lucene demo package. However, one thing I find surpring is that the > > write.lock file is left over,