AW: [lucene 4.6] NPE when calling IndexReader#openIfChanged

2014-05-18 Thread Clemens Wyss DEV
> delGen=-1 means there are no deletions, but the exception makes no > sense because up above SegmentReader.java calls si.hasDeletions() > which returns delGen != -1 which should have mean > Lucene40LiveDocsFormat.readLiveDocs should not have been called. It > seems impossible :) Possibly a co

Re: Best practice to map Lucene docids to real ids

2014-05-18 Thread Sven Teichmann
Thank you, that helped me a lot. Sven Teichmann __ Software for Intellectual Property GmbH Gewerbering 14a 83607 Holzkirchen (Germany) Phone: +49 (0)8024 46699-00 Fax:+49 (0)8024 46699-02 E-Mail: s.teichm...@s4ip.de Local Court of Munich

AW: [lucene 4.6] NPE when calling IndexReader#openIfChanged

2014-05-18 Thread Clemens Wyss DEV
Sorry for being imprecise java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) - Clemens -Ursprüngliche Nachricht- Von: Michael McCandless [mailto:luc...@mikemccandless.com] Gesendet: Sonntag, 18. Mai 2

How to use query terms tfidf as a factor in document similarity calculation

2014-05-18 Thread Diaa Abdallah
Hi, I'm trying to implement Explicit semantic analysis(ESA) via Lucene. How do I take a term TFIDF in a query into consideration when matching documents? For example: Query:"a b c a d a" Doc1:"a b a" Doc2:"a b c" The query should match Doc1 better than 2. I'd like this to work without impacting

Re: [lucene 4.6] NPE when calling IndexReader#openIfChanged

2014-05-18 Thread Michael McCandless
But what is the output of "java -fullversion"? Mike McCandless http://blog.mikemccandless.com On Sun, May 18, 2014 at 5:24 AM, Clemens Wyss DEV wrote: >> What java version? > We are still on (1.)6 > > -Ursprüngliche Nachricht- > Von: Michael McCandless [mailto:luc...@mikemccandless.com]

Re: best choice for ramBufferSizeMB

2014-05-18 Thread Michael McCandless
One thing to keep in mind is that a larger RAM buffer means less merging later, so even though the immediate observation is no speedup in indexing rate (and, likely, some slowdown), you are lowering the future merge cost, which is beneficial (it's a zero sum game!). Yes, stored fields as well as t

Search at LinkedIn tech talk on Wednesday

2014-05-18 Thread Sriram Sankar
I'm giving a talk that may be interesting to you: http://www.meetup.com/SF-Bay-Areas-Big-Data-Think-Tank/events/180573212/ Please share with others that may be interested. Sriram.

AW: [lucene 4.6] NPE when calling IndexReader#openIfChanged

2014-05-18 Thread Clemens Wyss DEV
> What java version? We are still on (1.)6 -Ursprüngliche Nachricht- Von: Michael McCandless [mailto:luc...@mikemccandless.com] Gesendet: Donnerstag, 15. Mai 2014 11:43 An: Lucene Users Betreff: Re: [lucene 4.6] NPE when calling IndexReader#openIfChanged delGen=-1 means there are no dele