Re: any good idea for loading fields into memory?

use collector and field cache is a good idea for ranking by certain field's value. but I just need to return matched documents' fields. and also field cache can't store multi-value fields? I have to store special chars like '\n' to separate them and split string to string array in runtime. On Fri,

Any CommonGrams-inspired tricks to speed up other proximity query types?

CommonGrams provides a neat trick for optimizing slow phrase queries that contain common words. (E.g. Hathi Trust has some datashowing how effective this can be.) Unfortunately, it does nothing for other positi

RE: any good idea for loading fields into memory?

I would ask the question that if you want to look at the whole value of a field during searching, why don't you have a just such a field in your index? I have an index with several fields that have 2 versions of the field both analyzed and unanalyzed. It works great for me in 3.x (not 4.x). Have

Re: any good idea for loading fields into memory?

I can't use 4.0 because it's not released. our company require to use stable version. So I decide to wrapper an IndexSearcher with fields' values in memory like this: and I copy all the codes of org.apache.lucene.search.SearcherManager. replace IndexSearcher with my IndexSearcherWithFields. any s