Re: multiple cache for same field

2013-05-27 Thread J Mohamed Zahoor
It does not seem to be memory footprint also ? looks too high for my index. ./zahoor On 20-May-2013, at 10:55 PM, Jason Hellman wrote: > Most definitely not the number of unique elements in each segment. My 32 > document sample index (built from the default example docs data) has the > fol

Re: multiple cache for same field

2013-05-20 Thread Jason Hellman
Most definitely not the number of unique elements in each segment. My 32 document sample index (built from the default example docs data) has the following: entry#0: 'StandardDirectoryReader(​segments_b:29 _8(​4.2.1):C32)'=>'manu_exact',class org.apache.lucene.index.SortedDocValues,0.5=>org.ap

Re: multiple cache for same field

2013-05-20 Thread Erick Erickson
Not sure, never had to worry about what they are.. On Mon, May 20, 2013 at 12:28 PM, J Mohamed Zahoor wrote: > > What is the number at the end? > is it the no of unique elements in each segment? > > ./zahoor > > > On 20-May-2013, at 7:37 PM, Erick Erickson wrote: > >> Because the same field

Re: multiple cache for same field

2013-05-20 Thread J Mohamed Zahoor
What is the number at the end? is it the no of unique elements in each segment? ./zahoor On 20-May-2013, at 7:37 PM, Erick Erickson wrote: > Because the same field is split amongst a number of segments. If you > look in the index directory, you should see files like _3fgm.* and > _3ffm.*. Eac

Re: multiple cache for same field

2013-05-20 Thread Erick Erickson
Because the same field is split amongst a number of segments. If you look in the index directory, you should see files like _3fgm.* and _3ffm.*. Each such group represents one segment. The number of segments changes with merging etc. Best Erick On Mon, May 20, 2013 at 6:43 AM, J Mohamed Zahoor w