Re: Optimizing number of segments in lucene index (no writes/deletes, only reads)

2017-06-13 Thread Riccardo Tasso
Hi, I have recently read this post, I think it will give you some hint: http://blog.trifork.com/2011/11/21/simon-says-optimize-is-bad-for-you/ Probably the only advantage of having one huge segment is to use less disk space. Riccardo 2017-06-14 5:23 GMT+02:00 Tom Hirschfeld : > Hello Fellow L

Optimizing number of segments in lucene index (no writes/deletes, only reads)

2017-06-13 Thread Tom Hirschfeld
Hello Fellow Lucene-eers, I have a lucene 6.5.1 app primarily indexed/searched via the latLonDocValuesField. The index is built once, and has no writes/deletes in production. At indexing time, we need to select the number of segments we want to generate, and it is unclear to us how many segments w

Re: Term Dictionary taking up lots of memory, looking for solutions, lucene 5.3.1

2017-06-13 Thread Tom Hirschfeld
Hey All, I was able to solve my problem a few weeks ago and wanted to update you all. The root issue was with the caching mechanism in "makedistancevaluesource" method in the lucene spatial module, it appears that documents were being pulled into the cache and not expired. To address this issue, w

Re: Odd Boolean Query behavior in SOLR 3.6

2017-06-13 Thread Erik Hatcher
Yes, fq’s make up constraints in conjunction with q. The issue here though is _clauses_.A single negative clause matches nothing. There is syntactic sugar at the Solr level to allow for q and fq’s to have a top-level single negative clause, like q=-type:pdf to return all non-pdf docs. Tha

Re: Odd Boolean Query behavior in SOLR 3.6

2017-06-13 Thread abhi Abhishek
Thanks Erik, This helped and the query is running and gives results as expected. Thanks for the insight, my understanding here was that fq parameter works on the result set of q parameter which is *:* here. shouldn't that be the case here? Thanks, Abhishek On Tue, Jun 13, 2017 at 6:02 PM, Erik

Re: Odd Boolean Query behavior in SOLR 3.6

2017-06-13 Thread Erik Hatcher
Inner purely negative queries match nothing. A query is about matching, and skipping over things that don’t match. The fix is when using (-something) to do (*:* -something) to match everything and skip the negative clause items. In your example, try fq=((*:* -documentTypeId:3) AND companyId:29

Odd Boolean Query behavior in SOLR 3.6

2017-06-13 Thread abhi Abhishek
Hi Everyone, I have hit a weird behavior of Boolean Query, when I am running the query with below param’s it’s not behaving as expected. can you please help me understand the behavior here? q=*:*&fq=((-documentTypeId:3)+AND+companyId:29096)&version=2.2&start=0&rows=10&indent=on