Re: Best practice to map Lucene docids to real ids

2014-05-12 Thread Sven Teichmann
Hi, I also found this response very useful and right now I am playing around with DocValues. If the default DocValuesFormat isn't fast enough, you can always switch to e.g. DirectDocValuesFormat (uses lots of RAM but it just an array lookup). How do I switch do DirectDocValuesFormat? And how do

Lucene: Index Writer to write in multiple file instead make one heavy file

2014-05-12 Thread Yogesh patel
HI I am using lucene 3.0.1. I am writing many documents with lucene Indexwriter. But Indexwriter add all documents into file which becomes more than 4GB in my case. so can i distribute files or partitioned ? -- *Regards,Yogesh Patel*

Why does QueryBuilder.createBooleanQuery create something different from input?

2014-05-12 Thread Cheng
Hi, I build a query using QueryBuilder.createBooleanQuery("title","【微信活动】6500盒“健康瘦身减肥”梅免费送"). When I check the query, the toString() of this query looks like: Query: title:而 title:不用 title:下载 title:2. title:目前 title:来说 title:已经 title:完美越狱 title:的人 title:没有 title:任何 title:必要 title:再用 title:红 titl

Re: Best practice to map Lucene docids to real ids

2014-05-12 Thread Wouter Heijke
Hey Mike, That was a very useful response, also for long time Lucene users like myself who were stuck in legacy ways of doing things! I managed to easily change indexing of keys to DocValues and found myself wondering why I did not get anything returned, it appears indexing works transparent to an

remapping docIds in a read only offline built index

2014-05-12 Thread Olivier Binda
In a 1-segment (parallel) read-only index, that is built offline once (and then frozen), is it possible to remap the docIds as the last step (i.e... to have the exact same index, except that the docIds are all equal to the ord the docs where added to the index) ? Say I have the read only index

ConcurrentModificationException in ICU analyzer

2014-05-12 Thread feedly team
I am using the 4.7.0 ICU analyzer (via elastic search) and noticed this exception in the logs. It's sporadic. Any ideas what is going on or if this is already fixed: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) at java.ut

MultiReader scoring

2014-05-12 Thread Tamer Gur
Dear lucene users, we are using lucene(4.6) MultiReader for different indexes and for performance reasons i am going to replace it with normal Reader. But we need to keep the scoring similar with MultiReader. and as expected when we switch to normal Reader scoring for each result is not same